View SYM53C896_3228411.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

? symbios ? SYM53C896 pci to dual channel ultra2 scsi multifunction controller order number s14015.a technical manual january 2000 version 3.0
ii this document contains proprietary information of lsi logic corporation. the information contained herein is not to be used by or disclosed to third parties without the express written permission of an of?cer of lsi logic corporation. lsi logic products are not intended for use in life-support appliances, devices, or systems. use of any lsi logic product in such applications without written consent of the appropriate lsi logic of?cer is prohibited. document db14-000083-01, second edition (january 2000) this document describes version 3.0 of lsi logic corporations symbios ? SYM53C896 pci to dual channel ultra2 scsi multifunction controller and will remain the of?cial reference source for all revisions/releases of this product until rescinded by an update. to receive product literature, visit us at http://www.lsilogic.com. lsi logic corporation reserves the right to make changes to any products herein at any time without notice. lsi logic does not assume any responsibility or liability arising out of the application or use of any product described herein, except as expressly agreed to in writing by lsi logic; nor does the purchase or use of a product from lsi logic convey a license under any patent rights, copyrights, trademark rights, or any other of the intellectual property rights of lsi logic or third parties. ultra scsi is the term used by the scsi trade association (sta) to describe fast-20 scsi, as documented in the scsi-3 fast-20 parallel interface standard, x3.277-199x. ultra2 scsi is the term used by the scsi trade association (sta) to describe fast-40 scsi, as documented in the scsi parallel interfaceC2 standard, (spiC2) x3t10/1142d. copyright ? 1997C2000 by lsi logic corporation. all rights reserved. trademark acknowledgment the lsi logic logo design, symbios, tolerant, scripts, and lvd link are registered trademarks or trademarks of lsi logic corporation. all other brand and product names may be trademarks of their respective companies.
contents iii contents chapter 1 introduction 1.1 general description 1-1 1.1.1 new features in the SYM53C896 1-3 1.2 bene?ts of ultra2 scsi 1-4 1.3 bene?ts of lvd link 1-4 1.4 tolerant ? technology 1-5 1.5 SYM53C896 bene?ts summary 1-6 1.5.1 scsi performance 1-6 1.5.2 pci performance 1-7 1.5.3 integration 1-8 1.5.4 ease of use 1-8 1.5.5 flexibility 1-8 1.5.6 reliability 1-9 1.5.7 testability 1-10 chapter 2 functional description 2.1 pci functional description 2-2 2.1.1 pci addressing 2-3 2.1.2 pci bus commands and functions supported 2-4 2.1.3 internal arbiter 2-10 2.1.4 pci cache mode 2-10 2.2 scsi functional description 2-18 2.2.1 scripts processor 2-18 2.2.2 internal scripts ram 2-19 2.2.3 64-bit addressing in scripts 2-20 2.2.4 hardware control of scsi activity led 2-20 2.2.5 designing an ultra2 scsi system 2-21 2.2.6 prefetching scripts instructions 2-22 2.2.7 opcode fetch burst capability 2-23
iv contents 2.2.8 load/store instructions 2-24 2.2.9 jtag boundary scan testing 2-24 2.2.10 scsi loopback mode 2-25 2.2.11 parity options 2-25 2.2.12 dma fifo 2-28 2.2.13 scsi bus interface 2-32 2.2.14 select/reselect during selection/reselection 2-38 2.2.15 synchronous operation 2-39 2.2.16 interrupt handling 2-41 2.2.17 interrupt routing 2-48 2.2.18 chained block moves 2-51 2.3 parallel rom interface 2-55 2.4 serial eeprom interface 2-57 2.4.1 default download mode 2-57 2.4.2 no download mode 2-58 2.5 power management 2-58 2.5.1 power state d0 2-59 2.5.2 power state d1 2-59 2.5.3 power state d2 2-60 2.5.4 power state d3 2-60 chapter 3 signal descriptions 3.1 internal pull-ups on SYM53C896 signals 3-4 3.2 pci bus interface signals 3-5 3.2.1 system signals 3-5 3.2.2 address and data signals 3-6 3.2.3 interface control signals 3-7 3.2.4 arbitration signals 3-8 3.2.5 error reporting signals 3-9 3.2.6 interrupt signals 3-10 3.2.7 scsi function a gpio signals 3-11 3.2.8 scsi function b gpio signals 3-12 3.3 scsi bus interface signals 3-13 3.3.1 scsi function a signals 3-13 3.3.2 scsi function b signals 3-16 3.4 rom flash and memory interface signals 3-19 3.5 test interface signals 3-20
contents v 3.6 power and ground signals 3-21 3.7 mad bus programming 3-23 chapter 4 registers 4.1 pci con?guration registers 4-1 4.2 scsi registers 4-20 4.3 64-bit scripts selectors 4-106 4.4 phase mismatch jump registers 4-109 chapter 5 scsi scripts instruction set 5.1 scsi scripts 5-1 5.1.1 sample operation 5-3 5.2 block move instructions 5-4 5.2.1 first dword 5-5 5.2.2 second dword 5-14 5.2.3 third dword 5-14 5.3 i/o instructions 5-15 5.3.1 first dword 5-15 5.3.2 second dword 5-22 5.4 read/write instructions 5-23 5.4.1 first dword 5-23 5.4.2 second dword 5-24 5.4.3 read-modify-write cycles 5-24 5.4.4 move to/from sfbr cycles 5-24 5.5 transfer control instructions 5-27 5.5.1 first dword 5-27 5.5.2 second dword 5-33 5.5.3 third dword 5-33 5.6 memory move instructions 5-34 5.6.1 first dword 5-35 5.6.2 read/write system memory from a scripts 5-35 5.6.3 second dword 5-36 5.6.4 third dword 5-36 5.7 load/store instructions 5-37 5.7.1 first dword 5-38 5.7.2 second dword 5-39
vi contents chapter 6 speci?cations 6.1 dc characteristics 6-1 6.2 tolerant technology electrical characteristics 6-7 6.3 ac characteristics 6-11 6.4 pci and external memory interface timing diagrams 6-13 6.4.1 target timing 6-15 6.4.2 initiator timing 6-22 6.4.3 external memory timing 6-38 6.5 scsi timing diagrams 6-58 appendix a register summary appendix b external memory interface diagram examples index customer feedback figures 1.1 typical SYM53C896 system application 1-2 1.2 typical SYM53C896 board application 1-3 2.1 SYM53C896 block diagram 2-2 2.2 parity checking/generation 2-28 2.3 dma fifo sections 2-29 2.4 SYM53C896 host interface scsi data paths 2-32 2.5 8-bit hvd wiring diagram for ultra scsi 2-36 2.6 regulated termination for ultra2 scsi 2-38 2.7 determining the synchronous transfer rate 2-41 2.8 interrupt routing hardware using the SYM53C896 2-50 2.9 block move and chained block move instructions 2-54 3.1 SYM53C896 functional signal grouping 3-2 5.1 scripts overview 5-4 5.2 block move instruction - first dword 5-5 5.3 block move instruction - second dword 5-14 5.4 block move instruction - third dword 5-14
contents vii 5.5 first 32-bit word of the i/o instruction 5-15 5.6 second 32-bit word of the i/o instruction 5-22 5.7 read/write instruction - first dword 5-23 5.8 read/write instruction - second dword 5-24 5.9 transfer control instructions - first dword 5-27 5.10 transfer control instructions - second dword 5-33 5.11 transfer control instructions - third dword 5-33 5.12 memory move instructions - first dword 5-35 5.13 memory move instructions - second dword 5-36 5.14 memory move instructions - third dword 5-36 5.15 load/store instruction - first dword 5-38 5.16 load/store instructions - second dword 5-39 6.1 lvd driver 6-2 6.2 lvd receiver 6-3 6.3 rise and fall time test condition 6-8 6.4 scsi input filtering 6-8 6.5 hysteresis of scsi receivers 6-9 6.6 input current as a function of input voltage 6-9 6.7 output current as a function of output voltage 6-10 6.8 external clock 6-11 6.9 reset input 6-12 6.10 interrupt output 6-12 6.11 pci con?guration register read 6-15 6.12 pci con?guration register write 6-16 6.13 operating registers/scripts ram read, 32-bit 6-17 6.14 operating register/scripts ram read, 64-bit 6-18 6.15 operating register/scripts ram write, 32-bit 6-19 6.16 operating register/scripts ram write, 64-bit 6-21 6.17 nonburst opcode fetch, 32-bit address and data 6-23 6.18 burst opcode fetch, 32-bit address and data 6-25 6.19 back-to-back read, 32-bit address and data 6-27 6.20 back-to-back write, 32-bit address and data 6-29 6.21 burst read, 32-bit address and data 6-31 6.22 burst read, 64-bit address and data 6-33 6.23 burst write, 32-bit address and data 6-35 6.24 burst write, 64-bit address and data 6-37 6.25 external memory read 6-39 6.26 external memory write 6-42
viii contents 6.27 normal/fast memory ( 3 128 kbytes) single byte access read cycle 6-44 6.28 normal/fast memory ( 3 128 kbytes) single byte access write cycle 6-46 6.29 normal/fast memory ( 3 128 kbytes) multiple byte access read cycle 6-48 6.30 normal/fast memory ( 3 128 kbytes) multiple byte access write cycle 6-50 6.31 slow memory ( 3 128 kbytes) read cycle 6-52 6.32 slow memory ( 3 128 kbytes) write cycle 6-54 6.33 64 kbytes rom read cycle 6-56 6.34 64 kbytes rom write cycle 6-57 6.35 initiator asynchronous send 6-58 6.36 initiator asynchronous receive 6-58 6.37 target asynchronous send 6-59 6.38 target asynchronous receive 6-59 6.39 initiator and target synchronous transfer 6-63 6.40 SYM53C896 329 bga (bottom view) 6-66 6.41 SYM53C896 329 bga mechanical drawing 6-67 b.1 16 kbyte interface with 200 ns memory b-1 b.2 64 kbyte interface with 150 ns memory b-2 b.3 128, 256, 512 kbyte or 1 mbyte interface with 150 ns memory b-3 b.4 512 kbyte interface with 150 ns memory b-4 tables 2.1 pci bus commands and encoding types for the SYM53C896 2-4 2.2 pci cache mode alignment 2-13 2.3 bits used for parity control and generation 2-26 2.4 scsi parity control 2-27 2.5 scsi parity errors and interrupts 2-27 2.6 hvd signals 2-34 2.7 parallel rom support 2-56 2.8 mode a serial eeprom data format 2-58 2.9 power states 2-59 3.1 SYM53C896 internal pull-ups and pull-downs 3-4 3.2 system signals 3-5
contents ix 3.3 address and data signals 3-6 3.4 interface control signals 3-7 3.5 arbitration signals 3-8 3.6 error reporting signals 3-9 3.7 interrupt signals 3-10 3.8 scsi function a gpio signals 3-11 3.9 scsi function b gpio signals 3-12 3.10 scsi bus interface signals 3-13 3.11 scsi function a signals 3-14 3.12 scsi function a_sctrl signals 3-15 3.13 scsi function b signals 3-16 3.14 scsi function b_scrtl signals 3-18 3.15 rom flash and memory interface signals 3-19 3.16 test interface signals 3-20 3.17 power and ground signals 3-21 3.18 decode of mad[3:1] pins 3-24 4.1 pci con?guration register map 4-2 4.2 scsi register map 4-21 4.3 examples of synchronous transfer periods and rates for scsi-1 4-35 4.4 example transfer periods and rates for fast scsi-2, ultra and ultra2 4-35 4.5 maximum synchronous offset 4-37 4.6 scsi synchronous data fifo word count 4-48 5.1 read/write instructions 5-25 6.1 absolute maximum stress ratings 6-1 6.2 operating conditions 6-2 6.3 lvd driver scsi signalssd[15:0], sdp[1:0], sreq/, sreq2/, sack/, sack2/, smsg/, sio/, scd/, satn/, sbsy/, ssel/, srst/ 6-2 6.4 lvd receiver scsi signalssd[15:0], sdp[1:0], sreq/, sreq2/, sack/, sack2/, smsg/, sio/, scd/, satn/, sbsy/, ssel/, srst/ 6-3 6.5 a and b diffsens scsi signals 6-3 6.6 input capacitance 6-3 6.7 bidirectional signalsgpio0_fetch/, gpio1_master/, gpio2, gpio3, gpio4, mad[7:0] 1 6-4 6.8 output signalsmas/[1:0], mce/, moe/_testout 1 ,
x contents mwe/, tdo 6-4 6.9 bidirectional signalsad[63:0], c_be[7:0]/, frame/, irdy/, trdy/, devsel/, stop/, perr/, par, par64, req64/, ack64/ 6-5 6.10 input signalsclk, gnt/, idsel, int_dir, rst/, sclk, tck, tdi, test_hsc, test_rst/, tms 6-5 6.11 output signalsinta, intb, alt_inta, alt_intb, req/ 6-6 6.12 output signalserr/ 6-6 6.13 tolerant technology electrical characteristics for se scsi signals 6-7 6.14 external clock 6-11 6.15 reset input 6-12 6.16 interrupt output 6-12 6.17 pci con?guration register read 6-15 6.18 pci con?guration register write 6-16 6.19 operating register/scripts ram read, 32-bit 6-17 6.20 operating register/scripts ram read, 64-bit 6-18 6.21 operating register/scripts ram write, 32-bit 6-19 6.22 operating register/scripts ram write, 64-bit 6-20 6.23 nonburst opcode fetch, 32-bit address and data 6-22 6.24 burst opcode fetch, 32-bit address and data 6-24 6.25 back-to-back read, 32-bit address and data 6-26 6.26 back-to-back write, 32-bit address and data 6-28 6.27 burst read, 32-bit address and data 6-30 6.28 burst read, 64-bit address and data 6-32 6.29 burst write, 32-bit address and data 6-34 6.30 burst write, 64-bit address and data 6-36 6.31 external memory read 6-38 6.32 external memory write 6-41 6.33 normal/fast memory ( 3 128 kbytes) single byte access read cycle 6-44 6.34 normal/fast memory ( 3 128 kbytes) single byte access write cycle 6-46 6.35 slow memory ( 3 128 kbytes) read cycle 6-52 6.36 slow memory ( 3 128 kbytes) write cycle 6-54 6.37 64 kbytes rom read cycle 6-56 6.38 64 kbytes rom write cycle 6-57
contents xi 6.39 initiator asynchronous send 6-58 6.40 initiator asynchronous receive 6-58 6.41 target asynchronous send 6-59 6.42 target asynchronous receive 6-59 6.43 scsi-1 transfers (se 5.0 mbytes) 6-60 6.44 scsi-1 transfers (differential 4.17 mbytes) 6-60 6.45 scsi-2 fast transfers 10.0 mbytes (8-bit transfers) or 20.0 mbytes (16-bit transfers) 40 mhz clock 6-61 6.46 scsi-2 fast transfers 10.0 mbytes (8-bit transfers) or 20.0 mbytes (16-bit transfers) 50 mhz clock 6-61 6.47 ultra scsi se transfers 20.0 mbytes (8-bit transfers) or 40.0 mbytes (16-bit transfers) quadrupled 40 mhz clock 6-62 6.48 ultra scsi hvd transfers 20.0 mbytes (8-bit transfers) or 40.0 mbytes (16-bit transfers) 80 mhz clock 6-62 6.49 ultra2 scsi transfers 40.0 mbyte (8-bit transfers) or 80.0 mbyte (16-bit transfers) quadrupled 40 mhz clock 6-63 6.50 signal names and bga position 6-64 6.51 signal names by bga position 6-65 a.1 SYM53C896 register map a-1
xii contents
preface xiii preface this book is the primary reference and technical manual for lsi logic corporations symbios ? SYM53C896 pci to dual channel ultra2 scsi multifunction controller. it contains a complete functional description for the product and includes complete physical and electrical speci?cations. audience this document was prepared for system designers and programmers who are using this device to design an ultra2 scsi port for pci-based personal computers, workstations, servers or embedded applications. organization this document has the following chapters and appendixes: chapter 1, introduction , describes the general information about the SYM53C896. chapter 2, functional description , describes the main functional areas of the chip in more detail, including the interfaces to the scsi bus and external memory. chapter 3, signal descriptions , contains the pin diagram and signal descriptions. chapter 4, registers , describes each bit in the operating registers, and is organized by register address. chapter 5, scsi scripts instruction set , de?nes all of the scsi scripts instructions that are supported by the SYM53C896. chapter 6, specifications , contains the electrical characteristics and ac timing diagrams. appendix a, register summary , is a register summary.
xiv preface appendix b, external memory interface diagram examples , contains several example interface drawings for connecting the SYM53C896 to external roms. related publications for background please contact: ansi 11 west 42nd street new york, ny 10036 (212) 642-4900 ask for document number x3.131-199x (scsi-2) global engineering documents 15 inverness way east englewood, co 80112 (800) 854-7179 or (303) 397-7956 (outside u.s.) fax (303) 397-2740 ask for document number x3.131-1994 (scsi-2) or x3.253 (scsi-3 parallel interface) endl publications 14426 black walnut court saratoga, ca 95070 (408) 867-6642 document names: scsi bench reference, scsi encyclopedia, scsi tutor prentice hall 113 sylvan avenue englewood cliffs, nj 07632 (800) 947-7700 ask for document number isbn 0-13-796855-8, scsi: understanding the small computer system interface lsi logic (storage components) electronic bulletin board (719) 533-7235 ask for document symbios ? pci to scsi i/o processors programming guide, order number j25972i
preface xv scsi electronic bulletin board (719) 533-7950 lsi logic world wide web home page www.lsil.com lsi logic internet anonymous ftp site ftp.symbios.com (204.131.200.1) directory: /pub/symchips/scsi pci special interest group 2575 n. e. katherine hillsboro, or 97214 (800) 433-5177; (503) 693-6232 (international); fax (503) 693-8344 conventions used in this manual the word assert means to drive a signal true or active. the word deassert means to drive a signal false or inactive. hexadecimal numbers are indicated by the pre?x 0x for example, 0x32cf. binary numbers are indicated by the pre?x 0b for example, 0b0011.0010.1100.1111. revision record revision date remarks 0.5 7/97 advanced information data - contains signal descriptions, registers, and mechanical drawings. 0.6 10/22/97 first draft - added: introduction, functional description, scsi scripts instruction set, electrical characteristics, register summary, and external memory interface diagram examples. 1.0 3/11/98 changes throughout to re?ect manual review process and preproduction chip revisions. 2.0 1/18/99 miscellaneous changes/corrections to re?ect product quali?cation. a table showing SYM53C896 internal pull-up and pull-downs has been added to chapter 3.
xvi preface 2.1 4/12/99 miscellaneous cosmetic/format changes from symbios to lsi logic. 3.0 11/99 final version. revision date remarks
symbios SYM53C896 pci to dual channel ultra2 scsi multifunction controller 1-1 chapter 1 introduction this chapter provides a general overview of the SYM53C896 pci to dual channel ultra2 scsi multifunction controller. the chapter contains the following sections: section 1.1, general description section 1.2, benefits of ultra2 scsi section 1.3, benefits of lvd link section 1.4, tolerant ? technology section 1.5, SYM53C896 benefits summary 1.1 general description the SYM53C896 pci to dual channel ultra2 scsi multifunction controller brings ultra2 scsi performance to host adapter, workstation, and general computer designs, making it easy to add a high-performance scsi bus to any pci system. it supports ultra2 scsi transfer rates and allows increased scsi connectivity and cable length with low voltage differential (lvd) signaling for scsi devices. the SYM53C896 has a local memory bus for local storage of the devices bios rom in ?ash memory or standard eproms. the SYM53C896 supports programming of local ?ash memory for updates to bios. the chip is packaged in a 329 ball grid array (bga) package. system diagrams showing the connections of the SYM53C896 with an external rom or ?ash memory are shown in appendix b, external memory interface diagram examples . lvd link? technology is the lsi logic implementation of lvd. lvd link transceivers allow the SYM53C896 to perform either single-ended (se) or lvd transfers, and support external high voltage differential (hvd) transceivers. the SYM53C896 integrates a high-performance scsi core,
1-2 introduction a 64-bit pci bus master dma core, and the lsi logic scsi scripts? processor to meet the ?exibility requirements of scsi-3 and ultra2 scsi standards. it is designed to implement multithreaded i/o algorithms with a minimum of processor intervention, solving the protocol overhead problems of previous intelligent and nonintelligent adapter designs. figure 1.1 illustrates a typical SYM53C896 system and figure 1.2 illustrates a typical SYM53C896 board application. figure 1.1 typical SYM53C896 system application fixed disk, optical disk, printer, tape, and other peripherals fixed disk, optical disk, printer, tape, and other peripherals one pci bus load pci graphic accelerator pci fast ethernet memory controller memory pci bus interface controller central processing unit (cpu) typical pci computer system architecture processor bus SYM53C896 pci to wide ultra2 scsi function a and SYM53C896 pci to wide ultra2 scsi function b scsi bus scsi bus
general description 1-3 figure 1.2 typical SYM53C896 board application 1.1.1 new features in the SYM53C896 the SYM53C896 is functionally similar to the sym53c876 pci to dual channel scsi multifunction controller, with added support for ultra2 scsi. some software enhancements, and the use of lvd, are needed to enable the chip to transfer data at ultra2 scsi transfer rates. 64-bit pci interface. able to handle scsi phase mismatches in scripts without interrupting the cpu. two wide ultra2 scsi channels in a single package. separate 8 kbyte internal scripts rams. jtag boundary scanning. raid ready alternative interrupt signaling. pc99 power management - including automatic download of subsystem vendor id and subsystem id, and pci power management levels d0, d1, d2, and d3. flash eeprom serial eeprom function a serial eeprom function b memory control block SYM53C896 64 bit pci to dual channel scsi controller function a 68 pin wide scsi connector scsi data, parity, and control signals function b 68 pin wide scsi connector scsi data, parity, and control signals pci interface pci address, data, parity and control signals memory address/data bus a_gpio/[1:0] b_gpio/[1:0]
1-4 introduction improved pci caching design - improves pci bus ef?ciency. load/store data transferred to or from scripts ram internal to chip. hardware control of scsi activity led. optional 944 byte dma fifo supports large block transfers at ultra2 scsi speeds. the default fifo size of 112 bytes is also supported. 32-bit istat registers ( interrupt status zero (istat0) , interrupt status one (istat1) , mailbox zero (mbox0) , mailbox one (mbox1) ). 1.2 bene?ts of ultra2 scsi ultra2 scsi is an extension of the spi-2 draft standard that allows faster synchronous scsi transfer rates and de?nes a new physical layer, lvd scsi, that provides an incremental evolution from scsi-2 and ultra scsi. when enabled, ultra2 scsi performs 40 mega transfers per second, which results in approximately double the synchronous transfer rates of ultra scsi. the SYM53C896 can perform 16-bit, ultra2 scsi synchronous transfers as fast as 80 mbytes/s on each channel for a total bandwidth of 160 mbytes/s. this advantage is most noticeable in heavily loaded systems, or large block size applications such as video on-demand and image processing. an advantage of ultra2 scsi is that it signi?cantly improves scsi bandwidth while preserving existing hardware and software investments. the primary software changes required are to enable the chip to perform synchronous negotiations for ultra2 scsi rates, and to enable the clock quadrupler. ultra2 scsi uses the same connectors as ultra scsi, but can operate with longer cables and more devices on the bus. chapter 2, functional description contains more information on migrating an ultra scsi design to an ultra2 scsi design. 1.3 bene?ts of lvd link the SYM53C896 supports lvd for scsi, a signaling technology that increases the reliability of scsi data transfers over longer distances than are supported by se scsi. the low current output of lvd allows the i/o transceivers to be integrated directly onto the chip. lvd provides the
tolerant ? technology 1-5 reliability of hvd scsi without the added cost of external differential transceivers. ultra2 scsi with lvd allows a longer scsi cable and more devices on the bus, with the same cables de?ned in the scsi-3 parallel interface standard for fast-20 (ultra scsi). lvd provides a long-term migration path to even faster scsi transfer rates without compromising signal integrity, cable length, or connectivity. for backward compatibility to existing se devices, the SYM53C896 features universal lvd link transceivers that can support lvd scsi, se, and hvd modes. the lvd link technology also supports hvd signaling in legacy systems, when external transceivers are connected to the SYM53C896. this allows the SYM53C896 to be used in both legacy and ultra2 scsi applications. 1.4 tolerant ? technology the SYM53C896 features tolerant technology, which includes active negation on the scsi drivers and input signal ?ltering on the scsi receivers. active negation causes the scsi request, acknowledge, data, and parity signals to be actively driven high rather than passively pulled up by terminators. active negation is enabled by setting bit 7 in the scsi test three (stest3) register. tolerant receiver technology improves data integrity in unreliable cabling environments, where other devices would be subject to data corruption. tolerant receivers ?lter the scsi bus signals to eliminate unwanted transitions, without the long signal delay associated with rc-type input ?lters. this improved driver and receiver technology helps eliminate double clocking of data, the single biggest reliability issue with scsi operations. tolerant input signal ?ltering is a built-in feature of the SYM53C896 and all lsi logic fast scsi, ultra scsi, and ultra2 scsi devices. the bene?ts of tolerant technology include increased immunity to noise when the signal is going high, better performance due to balanced duty cycles, and improved fast scsi transfer rates. in addition, tolerant scsi devices do not cause glitches on the scsi bus at power-up or power-down, so other devices on the bus are also protected from data corruption. when it is used with the lvd link transceivers, tolerant technology provides excellent signal quality and data reliability in real
1-6 introduction world cabling environments. tolerant technology is compatible with both the alternative one and alternative two termination schemes proposed by the american national standards institute. 1.5 SYM53C896 bene?ts summary this section provides an overview of the SYM53C896 features and bene?ts. it contains information on scsi performance , pci performance , integration , ease of use , flexibility , reliability , and testability . 1.5.1 scsi performance has integrated lvd link universal transceivers which: C support se, lvd, and hvd signals (with external transceivers). C allow greater device connectivity and longer cable length. C lvd link transceivers save the cost of external differential transceivers. C supports a long-term performance migration path. with a 944 byte fifo, the chip can ef?ciently burst up to 512 bytes across the pci bus. two separate scsi channels on one chip. performs wide, ultra2 scsi synchronous transfers as fast as 80 mbytes/s on each scsi channel for a total of 160 mbytes/s. can handle phase mismatches in scripts without interrupting the system processor. on-chip scsi clock quadrupler allows the chip to achieve ultra2 scsi transfer rates with an input frequency of 40 mhz. includes 8 kbytes of internal ram for scripts instruction storage for each scsi channel. 31 levels of scsi synchronous offset. supports variable block size and scatter/gather data transfers. performs sustained memory-to-memory dma transfers to approximately 100 mbytes/s. minimizes scsi i/o start latency.
SYM53C896 bene?ts summary 1-7 performs complex bus sequences without interrupts, including restoring data pointers. reduces isr overhead through a unique interrupt status reporting method. load/store scripts instructions increase performance of data transfers to and from the chip registers without using pci cycles. scripts support of 64-bit addressing. supports target disconnect and later reconnect with no interrupt to the system processor. supports multithreaded i/o algorithms in scsi scripts with fast i/o context switching. expanded register move instruction supports additional arithmetic capability. 1.5.2 pci performance complies with the pci 2.1 speci?cation. 64-bit or 32-bit 33 mhz pci interface. C dual address cycle (dac) can be generated for all scripts. C true pci multifunction device - presents one electrical load to the pci bus. bursts 2/4, 4/8, 8/16, 16/32, 32/64, or 64/128 qword/dword transfers across the pci bus. supports 64-bit or 32-bit word data bursts with variable burst lengths. prefetches up to 8 dwords of scripts instructions. bursts scripts opcode fetches across the pci bus. performs zero wait-state bus master data bursts up to 264 mbytes/s (@ 33 mhz). supports pci cache line size register. supports pci write and invalidate, read line, and read multiple commands. complies with pci bus power management speci?cation rev 1.1.
1-8 introduction 1.5.3 integration dual channel ultra2 scsi pci multifunction controller. integrated lvd transceivers. full 64-bit or 32-bit pci dma bus master. can be used as a third-party pci bus dma controller by using memory-to-memory move instructions. integrated scripts processor. 1.5.4 ease of use up to one megabyte of add-in memory support for bios and scripts storage. direct pci to scsi connection. reduced scsi development effort. compiler-compatible with existing sym53c7xx and sym53c8xx family scripts. direct connection to pci and scsi se, lvd and hvd (needs external transceivers). development tools and sample scsi scripts available. maskable and pollable interrupts. wide scsi, a or p cable, and up to 15 devices per scsi channel supported. three programmable scsi timers: select/reselect, handshake-to-handshake, and general purpose. the time-out period is programmable from 100 m s to greater than 25.6 seconds. software for pc-based operating system support. support for relative jumps. scsi selected as id bits for responding with multiple ids. 1.5.5 flexibility universal lvd transceivers are backward compatible with se or hvd devices. high level programming interface (scsi scripts).
SYM53C896 bene?ts summary 1-9 programs local and bus ?ash memory. selectable 112 or 944 byte dma fifo for backward compatibility. tailored scsi sequences execute from main system ram or internal scripts ram. flexible programming interface to tune i/o performance or to adapt to unique scsi devices. support for changes in the logical i/o interface de?nition. low level access to all registers and all scsi bus signals. fetch, master, and memory access control pins. separate scsi and system clocks. scsi clock quadrupler bits enable ultra2 scsi transfer rates with a 40 mhz scsi clock input. selectable irq pin disable bit. ability to route system clock to scsi clock. compatible with 3.3 v and 5 v pci. 1.5.6 reliability 2 kv esd protection on scsi signals. protection against bus re?ections due to impedance mismatches. controlled bus assertion times (reduces rfi, improves reliability, and eases fcc certi?cation). latch-up protection greater than 150 ma. voltage feed-through protection (minimum leakage current through scsi pads). more than 25% of pins are power and ground. power and ground isolation of i/o pads and internal chip logic. tolerant technology provides: C active negation of scsi data, parity, request, and acknowledge signals for improved fast scsi transfer rates. C input signal ?ltering on scsi receivers improves data integrity, even in noisy cabling environments.
1-10 introduction 1.5.7 testability all scsi signals accessible through programmed i/o. scsi loopback diagnostics. scsi bus signal continuity checking. support for single step mode operation. jtag boundary scan.
symbios SYM53C896 pci to dual channel ultra2 scsi multifunction controller 2-1 chapter 2 functional description chapter 2 is divided into the following sections: section 2.1, pci functional description section 2.2, scsi functional description section 2.3, parallel rom interface section 2.4, serial eeprom interface section 2.5, power management the SYM53C896 pci to dual channel ultra2 scsi multifunction controller is composed of the following modules: 64-bit pci interface. two independent pci-to-wide ultra2 scsi controllers. rom/flash memory controller. serial eeprom controller. figure 2.1 illustrates the relationship between these modules.
2-2 functional description figure 2.1 SYM53C896 block diagram 2.1 pci functional description the SYM53C896 implements two pci-to-wide ultra2 scsi controllers in a single package. this con?guration presents only one load to the pci bus and uses one req/ - gnt/ pair to arbitrate for pci bus mastership. however, separate interrupt signals are generated for scsi function a and scsi function b. 8 kbyte scripts ram 8 dword scripts prefetch buffer operating registers scsi scripts processor 944 byte dma fifo scsi fifo and scsi control block universal tolerant drivers and receivers 64-bit pci interface, pci con?guration registers (2 sets) wide ultra2 scsi controller serial eeprom controller and autocon?guration rom/flash memory control local bus memory 8 kbyte scripts ram 8 dword scripts prefetch buffer scsi scripts processor 944 byte dma fifo scsi fifo and scsi control block universal tolerant drivers and receivers wide ultra2 scsi controller operating registers pci bus scsi function b wide ultra2 scsi bus scsi function a wide ultra2 scsi bus jtag rom/flash memory bus 2-wire serial eeprom bus (function a) 2-wire serial eeprom bus (function b)
pci functional description 2-3 2.1.1 pci addressing there are three physical pci-de?ned address spaces: pci configuration space . i/o space for operating registers. memory space for operating registers. 2.1.1.1 con?guration space the host processor uses this con?guration space to initialize the SYM53C896. two independent sets of con?guration space registers are de?ned, one set for each scsi function. the con?guration registers are accessible only by system bios during pci con?guration cycles. each con?guration space is a contiguous 256 x 8-bit set of addresses. decoding c_be[3:0]/ determines if a pci cycle is intended to access the con?guration register space. the idsel bus signal is a chip select that allows access to the con?guration register space only. a con?guration read/write cycle without idsel is ignored. the eight lower order address bits (ad[7:0]) are used to select a speci?c 8-bit register. since the SYM53C896 is a pci multifunction device, bits ad[10:8] decode either scsi function a con?guration register (ad[10:8] = 0b000) or scsi function b con?guration register (ad[10:8] = 0b001). at initialization time, each pci device is assigned a base address (in the case of the SYM53C896, the upper 24 bits of the address are selected) for memory accesses and i/o accesses. on every access, the SYM53C896 compares its assigned base addresses with the value on the address/data bus during the pci address phase. if there is a match of the upper 24 bits, the access is for the SYM53C896 and the low-order eight bits de?ne the register to be accessed. a decode of c_be[3:0]/ determines which registers and what type of access is to be performed. i/o space C the pci speci?cation de?nes i/o space as a contiguous 32-bit i/o address that is shared by all system resources, including the SYM53C896. base address register zero determines which 256-byte i/o area this device occupies. memory space C the pci speci?cation de?nes memory space as a contiguous 64-bit memory address that is shared by all system resources, including the SYM53C896. base address register one determines which 1 kbyte memory area this device occupies. each scsi function uses a 8 kbyte scripts ram memory space. base address
2-4 functional description register two determines the 8 kbyte memory area the scripts ram occupies. 2.1.2 pci bus commands and functions supported bus commands indicate to the target the type of transaction the master is requesting. bus commands are encoded on the c_be[3:0]/ lines during the address phase. pci bus commands and encoding types appear in table 2.1 . table 2.1 pci bus commands and encoding types for the SYM53C896 c_be[3:0]/ command type supported as master supported as slave 0000 interrupt acknowledge no no 0001 special cycle no no 0010 i/o read yes yes 0011 i/o write yes yes 0100 reserved n/a n/a 0101 reserved n/a n/a 0110 memory read yes yes 0111 memory write yes yes 1000 reserved n/a n/a 1001 reserved n/a n/a 1010 con?guration read no yes 1011 con?guration write no yes 1100 memory read multiple yes 1 yes (defaults to 0110) 1101 dac yes yes 1110 memory read line yes 1 yes (defaults to 0110) 1111 memory write and invalidate yes 2 yes (defaults to 0111) 1. see the dma mode (dmode) register. 2. see the chip test three (ctest3) register.
pci functional description 2-5 2.1.2.1 interrupt acknowledge command the SYM53C896 does not respond to this command as a slave and it never generates this command as a master. 2.1.2.2 special cycle command the SYM53C896 does not respond to this command as a slave and it never generates this command as a master. 2.1.2.3 i/o read command the i/o read command reads data from an agent mapped in the i/o address space. all 64 address bits are decoded. 2.1.2.4 i/o write command the i/o write command writes data to an agent mapped in the i/o address space. all 64 address bits are decoded. 2.1.2.5 reserved command the SYM53C896 does not respond to this command as a slave and it never generates this command as a master. 2.1.2.6 memory read command the memory read command reads data from an agent mapped in the memory address space. the target is free to do an anticipatory read for this command only if it can guarantee that such a read has no side effects. 2.1.2.7 memory write command the memory write command writes data to an agent mapped in the memory address space. when the target returns ready, it assumes responsibility for the coherency (which includes ordering) of the subject data. 2.1.2.8 con?guration read command the con?guration read command reads the con?guration space of each agent. an agent is selected during a con?guration access when its
2-6 functional description idsel signal is asserted and ad[1:0] are 0b00. during the address phase of a con?guration cycle ad[7:2] addresses one of the 64 dword registers (where byte enables address the bytes within each dword) in the con?guration space of each device. ad[63:11] are logical dont cares to the selected agent. ad[10:8] indicate which device of a multifunction agent is being addressed. 2.1.2.9 con?guration write command the con?guration write command transfers data to the con?guration space of each agent. an agent is selected when its idsel signal is asserted and ad[1:0] are 0b00. during the address phase of a con?guration cycle, the ad[7:2] lines address the 64 dword registers (where byte enables address the bytes within each dword) in the con?guration space of each device. ad[63:11] are logical dont cares to the selected agent. ad[10:8] indicate which device of a multifunction agent is addressed. 2.1.2.10 memory read multiple command this command is identical to the memory read command except that it additionally indicates that the master may intend to fetch more than one cache line before disconnecting. the SYM53C896 supports pci memory read multiple functionality and issues memory read multiple commands on the pci bus when the read multiple mode is enabled. this mode is enabled by setting bit 2 (ermp) of the dma mode (dmode) register. if cache mode is enabled, a memory read multiple command is issued on all read cycles, except opcode fetches, when the following conditions are met: the clse bit (cache line size enable, bit 7, dma control (dcntl) register) and the ermp bit (enable read multiple, bit 2, dma mode (dmode) register) are set. the cache line size register for each function contains a legal burst size value (2, 4, 8, 16, 32, or 64) and that value is less than or equal to the dmode burst size. the transfer will cross a cache line boundary. when these conditions are met, the chip issues a memory read multiple command instead of a memory read during all pci read cycles.
pci functional description 2-7 burst size selection C the read multiple command reads in multiple cache lines of data in a single bus ownership. the number of cache lines to read is a multiple of the cache line size speci?ed in revision 2.1 of the pci speci?cation. the logic selects the largest multiple of the cache line size based on the amount of data to transfer, with the maximum allowable burst size determined from the dma mode (dmode) burst size bits, and the chip test five (ctest5) , bit 2. 2.1.2.11 dac command the SYM53C896 performs dacs when 64-bit addressing is required. see pci speci?cation 2.1. if any of the selector registers contain a nonzero value, a dac will be generated. 2.1.2.12 memory read line command this command is identical to the memory read command, except that it additionally indicates that the master intends to fetch a complete cache line. this command is intended for use with bulk sequential data transfers where the memory system and the requesting master might gain some performance advantage by reading to a cache line boundary rather than a single memory cycle. the read line function in the SYM53C896 takes advantage of the pci 2.1 speci?cation regarding issuing of this command. if the cache mode is disabled, read line commands will not be issued. if the cache mode is enabled, a read line command is issued on all read cycles, except nonprefetch opcode fetches, when the following conditions are met: the clse (cache line size enable, bit 7, of the dma control (dcntl) register) and erl (enable read line, bit 3, of the dma mode (dmode) register) bits are set. the cache line size register for each function must contain a legal burst size value in dwords (2, 4, 8, 16, 32, 64, or 128) and that value is less than or equal to the dmode burst size. the transfer will cross a dword boundary but not a cache line boundary.
2-8 functional description when these conditions are met, the chip issues a read line command instead of a memory read during all pci read cycles. otherwise, it issues a normal memory read command. read multiple with read line enabled C when both the read multiple and read line modes are enabled, the read line command is not issued if the above conditions are met. instead, a read multiple command is issued, even though the conditions for read line are met. if the read multiple mode is enabled and the read line mode is disabled, read multiple commands are issued if the read multiple conditions are met. 2.1.2.13 memory write and invalidate command the memory write and invalidate command is identical to the memory write command, except that it additionally guarantees a minimum transfer of one complete cache line. that is, the master intends to write all bytes within the addressed cache line in a single pci transaction unless interrupted by the target. this command requires implementation of the pci cache line size register at address 0x0c in pci con?guration space. the SYM53C896 enables memory write and invalidate cycles when bit 0 (wrie) in the chip test three (ctest3) register and bit 4 (wie) in the pci command register are set. when the following conditions are met, memory write and invalidate commands are issued: 1. the clse bit (cache line size enable, bit 7, of the dma control (dcntl) register), wrie bit (write and invalidate enable, bit 0, of the chip test three (ctest3) register), and pci con?guration command register, bit 4 are set. 2. the cache line size register for each function contains a legal burst size value in dwords (2, 4, 8, 16, 32, 64, or 128) and that value is less than or equal to the dma mode (dmode) burst size. 3. the chip has enough bytes in the dma fifo to complete at least one full cache line burst. 4. the chip is aligned to a cache line boundary. when these conditions are met, the SYM53C896 issues a write and invalidate command instead of a memory write command during all pci write cycles.
pci functional description 2-9 multiple cache line transfers C the memory write and invalidate command can write multiple cache lines of data in a single bus ownership. the chip issues a burst transfer as soon as it reaches a cache line boundary. the size of the transfer is not automatically the cache line size, but rather a multiple of the cache line size speci?ed in revision 2.1 of the pci speci?cation. the logic selects the largest multiple of the cache line size based on the amount of data to transfer, with the maximum allowable burst size determined from the dma mode (dmode) burst size bits, and chip test five (ctest5) , bit 2. if multiple cache line size transfers are not desired, set the dmode burst size to exactly the cache line size and the chip only issues single cache line transfers. after each data transfer, the chip re-evaluates the burst size based on the amount of remaining data to transfer and again selects the highest possible multiple of the cache line size, and no larger than the dma mode (dmode) burst size. the most likely scenario of this scheme is that the chip selects the dmode burst size after alignment, and issues bursts of this size. the burst size is, in effect, throttled down toward the end of a long memory move or block move transfer until only the cache line size burst size is left. the chip ?nishes the transfer with this burst size. latency C in accordance with the pci speci?cation, the latency timer is ignored when issuing a memory write and invalidate command such that when a latency time-out occurs, the SYM53C896 continues to transfer up to a cache line boundary. at that point, the chip relinquishes the bus, and ?nishes the transfer at a later time using another bus ownership. if the chip is transferring multiple cache lines it continues to transfer until the next cache boundary is reached. pci target retry C during a memory write and invalidate transfer, if the target device issues a retry (stop with no trdy/, indicating that no data was transferred), the chip relinquishes the bus and immediately tries to ?nish the transfer on another bus ownership. the chip issues another memory write and invalidate command on the next ownership, in accordance with the pci speci?cation. pci target disconnect C during a memory write and invalidate transfer, if the target device issues a disconnect the SYM53C896 relinquishes the bus and immediately tries to ?nish the transfer on another bus ownership. the chip does not issue another memory write
2-10 functional description and invalidate command on the next ownership unless the address is aligned. 2.1.3 internal arbiter the pci to scsi controller uses a single req/ - gnt/ signal pair to arbitrate for access to the pci bus. an internal arbiter circuit allows the different bus mastering functions resident in the chip to arbitrate among themselves for the privilege of arbitrating for pci bus access. there are two independent bus mastering functions inside the SYM53C896, one for each of the scsi functions. the internal arbiter uses a round robin arbitration scheme to decide which internal bus mastering function may arbitrate for access to the pci bus. this ensures that no function is starved for access to the pci bus. 2.1.4 pci cache mode the SYM53C896 supports the pci speci?cation for an 8-bit cache line size register located in the pci con?guration space. the cache line size register provides the ability to sense and react to nonaligned addresses corresponding to cache line boundaries. in conjunction with the cache line size register, the pci commands memory read line, memory read multiple, memory write and invalidate are each software enabled or disabled to allow the user full ?exibility in using these commands. 2.1.4.1 enabling cache mode for the cache logic to be enabled to issue pci cache commands (memory read line, memory read multiple, and memory write and invalidate) on any given pci master operation the following conditions must be met: the cache line size enable bit in the dma control (dcntl) register must be set. the pci cache line size register must contain a valid binary cache size, i.e. 2, 4, 8, 16, 32, 64, or 128 dwords. only these values are considered valid cache sizes. the programmed burst size (in dwords) must be equal to or greater than the cache line size register. the dma mode (dmode) register bits [7:6] and the chip test five (ctest5) register bit 2 are the burst length bits.
pci functional description 2-11 the part must be doing a pci master transfer. the following pci master transactions do not utilize the pci cache logic and thus no pci cache commands will be issued during these types of cycles: a nonprefetch scripts fetch, a load/store data transfer, a data ?ush operation. all other types of pci master transactions will utilize the pci cache logic. the above four conditions must be met for the cache logic to control the type of pci cache command that is issued, along with any alignment that may be necessary during write operations. if these conditions are not met for any given pci master transaction, a memory read or memory write will be issued and no cache write alignment will be done. 2.1.4.2 issuing cache commands in order to issue each type of pci cache command, the corresponding enable bit must be set (2 bits in the case of memory write and invalidate). to issue memory read line commands, set the memory read line enable bit in the dma mode (dmode) register. to issue memory read multiple commands, set the read multiple enable bit in the dma mode (dmode) register. to issue memory write and invalidate commands, set the write and invalidate enables in both the chip test three (ctest3) and the pci con?guration command registers. if the corresponding cache command that is to be issued is not enabled then the cache logic will fall back to the next command enabled, i.e., if memory read multiple is not enabled and memory read lines are, read lines will be issued in place of read multiples. if no cache commands are enabled, cache write alignment will still occur but no cache commands will be issued, only memory reads and memory writes will be issued. 2.1.4.3 memory read caching which type of memory read command gets issued depends on the starting location of the transfer and the number of bytes to be transferred. during reads, no cache alignment is done (this is not required nor optimal per pci 2.1 speci?cation) and reads will always be either a programmed burst length in size, as set in the dma mode (dmode) and
2-12 functional description chip test three (ctest3) registers. in the case of a transfer which is smaller than the burst length, all bytes for that transfer will be read in one pci burst transaction. if the transfer will cross a dword boundary (a[1:0] = 0b00) a memory read line command is issued. when the transfer will cross a cache boundary (depends on the cache line size programmed into the pci con?guration register), a memory read multiple command is issued. if a transfer will not cross a dword or cache boundary or if cache mode is not enabled a memory read command is issued. 2.1.4.4 memory write caching writes will be aligned in a single burst transfer to get to a cache boundary. at that point, memory write and invalidate commands will be issued and will continue at the burst length programmed into the dma mode (dmode) register. memory write and invalidate commands are issued as long as the remaining byte count is greater than the memory write and invalidate threshold. when the byte count goes below this threshold, a single memory write burst will be issued to complete the transfer. the general pattern for pci writes will is: a single memory write to align to a cache boundary. multiple memory write and invalidates. a single data residual memory write to complete the transfer.
pci functional description 2-13 table 2.2 pci cache mode alignment host memory a 00h b 04h 08h c 0ch d 10h 14h 18h 1ch e 20h 24h 28h 2ch f 30h 34h 38h 3ch g 40h 44h 48h 4ch h 50h 54h 58h 5ch 60h
2-14 functional description 2.1.4.5 examples: mr = memory read, mrl = memory read line, mrm = memory read multiple, mw = memory write, mwi = memory write and invalidate. read example 1 C burst = 4 dwords, cache line size = 4 dwords: atob: mrl (6 bytes) atoc: mrl (13 bytes) atod: mrl (15 bytes) mr (2 bytes) ctod: mrm (5 bytes) ctoe: mrm (15 bytes) mrm (6 bytes) dtof: mrl (15 bytes) mrl (16 bytes) mr (1 byte) atoh: mrl (15 bytes) mrl (16 bytes) mrl (16 bytes) mrl (16 bytes) mrl (16 bytes) mr (2 bytes) atog: mrl (15 bytes) mrl (16 bytes) mrl (16 bytes) mrl (16 bytes) mr (3 bytes)
pci functional description 2-15 read example 2 C burst = 8 dwords, cache line size = 4 dwords: read example 3 C burst = 16 dwords, cache line size = 8 dwords: atob: mrl (6 bytes) atoc: mrl (13 bytes) atod: mrm (17 bytes) ctod: mrm (5 bytes) ctoe: mrm (21 bytes) dtof: mrm (31 bytes) mr (1 byte) atoh: mrm (31 bytes) mrm (32 bytes) mrm (18 bytes) atog: mrm (31 bytes) mrm (32 bytes) mr (3 bytes) atob: mrl (6 bytes) atoc: mrl (13 bytes) atod: mrl (17 bytes) ctod: mrl (5 bytes) ctoe: mrm (21 bytes) dtof: mrm (32 bytes) atoh: mrm (63 bytes) mrl (16 bytes) mrm (2 bytes) atog: mrm (63 bytes) mr(3 bytes)
2-16 functional description write example 1 C burst = 4 dwords, cache line size = 4 dwords: write example 2 C burst = 8 dwords, cache line size = 4 dwords: atob: mw (6 bytes) atoc: mw (13 bytes) atod: mw (17 bytes) ctod: mw (5 bytes) ctoe: mw (3 bytes) mwi (16 bytes) mw (2 bytes) dtof: mw (15 bytes) mwi (16 bytes) mw (1 byte) atoh: mw (15 bytes) mwi (16 bytes) mwi (16 bytes) mwi (16 bytes) mwi (16 bytes) mw (2 bytes) atog: mw (15 bytes) mwi (16 bytes) mwi (16 bytes) mwi (16 bytes) mw (3 bytes) atob: mw (6 bytes) atoc: mw (13 bytes) atod: mw (17 bytes) ctod: mw (5 bytes) ctoe: mw (3 bytes) mwi (16 bytes) mw (2 bytes) dtof: mw (15 bytes) mwi (16 bytes) mw (1 byte)
pci functional description 2-17 write example 3 C burst = 16 dwords, cache line size = 8 dwords: 2.1.4.6 memory-to-memory moves memory-to-memory moves also support pci cache commands, as described above, with one limitation: memory write and invalidate on memory-to-memory move writes are only supported if the source and destination address are quad word aligned. if the source and destination are not quad word aligned, that is, source address[2:0] == destination address[2:0], write aligning is not performed and no memory write and invalidate commands are issued. the SYM53C896 is little endian only. atoh: mw (15 bytes) mwi (32 bytes) mwi (32 bytes) mw (2 bytes) atog: mw (15 bytes) mwi (32 bytes) mwi (16 bytes) mw (3 bytes) atob: mw (6 bytes) atoc: mw (13 bytes) atod: mw (17 bytes) ctod: mw (5 bytes) ctoe: mw (21 bytes) dtof: mw (32 bytes) atoh: mw (15 bytes) mwi (64 bytes) mw (2 bytes) atog: mw (15 bytes) mwi (32 bytes) mw (18 bytes)
2-18 functional description 2.2 scsi functional description the SYM53C896 provides two ultra2 scsi controllers on a single chip. each ultra2 scsi controller provides a scsi function that supports an 8-bit or 16-bit bus. each controller supports wide ultra2 scsi synchronous transfer rates up to 80 mbytes/s on a lvd scsi bus. scsi functions can be programmed with scsi scripts, making it easy to ?ne tune the system for speci?c mass storage devices or ultra2 scsi requirements. the SYM53C896 offers low level register access or a high-level control interface. like ?rst generation scsi devices, the SYM53C896 is accessed as a register-oriented device. the ability to sample and/or assert any signal on the scsi bus is used in error recovery and diagnostic procedures. in support of scsi loopback diagnostics, each scsi function may perform a self-selection and operate as both an initiator and a target. the SYM53C896 is controlled by the integrated scripts processor through a high-level logical interface. commands controlling the scsi functions are fetched out of the main host memory or local memory. these commands instruct the scsi functions to select, reselect, disconnect, wait for a disconnect, transfer information, change bus phases and, in general, implement all aspects of the scsi protocol. the scripts processor is a special high-speed processor optimized for scsi protocol. 2.2.1 scripts processor the scsi scripts processor allows both dma and scsi commands to be fetched from host memory or internal scripts ram. algorithms written in scsi scripts control the actions of the scsi and dma cores. the scripts processor executes complex scsi bus sequences independently of the host cpu. algorithms may be designed to tune scsi bus performance, to adjust to new bus device types (such as scanners, communication gateways, etc.), or to incorporate changes in the scsi-2 or scsi-3 logical bus de?nitions without sacri?cing i/o performance. scsi scripts are hardware independent, so they can be used interchangeably on any host or cpu
scsi functional description 2-19 system bus. scsi scripts also handle conditions such as phase mismatch. 2.2.1.1 phase mismatch handling in scripts the SYM53C896 can handle phase mismatches due to drive disconnects without needing to interrupt the processor. the primary goal of this logic is to completely eliminate the need for cpu intervention during an i/o disconnect/reselect sequence. storing the appropriate information to later restart the i/o can be done through scripts, eliminating the need for processor intervention during an i/o disconnect/reselect sequence. calculations are performed such that the appropriate information is available to scripts so that an i/o state can be properly stored for restart later. the phase mismatch jump logic powers up disabled and must be enabled by setting the phase mismatch jump enable bit (enpmj, bit 7 in the chip control 0 (ccntl0) register). utilizing the information supplied in the phase mismatch jump address 1 (pmjad1) and phase mismatch jump address 2 (pmjad2) registers, described in chapter 4, registers , allows all overhead involved in a disconnect/reselect sequence to be handled with a modest amount of scripts instructions. 2.2.2 internal scripts ram the SYM53C896 has 8 kbytes (2048 x 32 bits) of internal, general purpose ram for each scsi function. the ram is designed for scripts program storage, but is not limited to this type of information. when the chip fetches scripts instructions or table indirect information from the internal ram, these fetches remain internal to the chip and do not use the pci bus. other types of access to the ram by the chip, except load/store, use the pci bus as if they were external accesses. the scripts ram powers up enabled by default. the ram can be relocated by the pci system bios anywhere in the 64-bit address space. base address register two (scripts ram) in the pci con?guration space contains the base address of the internal ram. to simplify loading of the scripts instructions, the base address of the ram appears in the scratch register b (scratchb) register when bit 3
2-20 functional description of the chip test two (ctest2) register is set. the upper 32 bits of a 64- bit base address will be in the scripts fetch selector (sfs) register. the ram is byte accessible from the pci bus and is visible to any bus mastering device on the bus. external accesses to the ram (by the cpu) follow the same timing sequence as a standard slave register access, except that the required target wait-states drop from 5 to 3. a complete set of development tools is available for writing custom drivers with scsi scripts. for more information on the scsi scripts instructions supported by the SYM53C896, see chapter 5, scsi scripts instruction set . 2.2.3 64-bit addressing in scripts the SYM53C896 has a 64-bit pci interface which provides 64-bit address and data capability in the initiator mode. the chip can also respond to 64-bit addressing in the target mode. dacs can be generated for all scripts operations. there are six selector registers which hold the upper dword of a 64-bit address. all but one of these is static and requires manual loading using a cpu access, a load/store instruction, or a memory move instruction. one of the selector registers is dynamic and is used during 64-bit direct block moves only. all selectors will default to zero, meaning the SYM53C896 will power-up in a state where only single address cycles (sacs) will be generated. when any of the selector registers are written to a nonzero value, dacs will be generated. direct, table indirect and indirect block moves, memory-to-memory moves, load/stores and jumps are all instructions with 64-bit address capability. crossing the 4 gbyte boundary on any one scripts operation is not permitted and software needs to take care that any given scripts operation will not cross the 4 gbyte boundary. 2.2.4 hardware control of scsi activity led the SYM53C896 has the ability to control a led through the gpio_0 pin to indicate that it is connected to the scsi bus. formerly this function was done by a software driver.
scsi functional description 2-21 when bit 5 (led_cntl) in the general purpose pin control (gpcntl) register is set and bit 6 (fetch enable) in the gpcntl register is cleared and the SYM53C896 is not performing an eeprom autodownload, then bit 3 (con) in the interrupt status zero (istat0) register will be presented at the gpio_0 pin. the con (connected) bit in interrupt status zero (istat0) will be set anytime the SYM53C896 is connected to the scsi bus either as an initiator or a target. this will happen after the SYM53C896 has successfully completed a selection or when it has successfully responded to a selection or reselection. it will also be set when the SYM53C896 wins arbitration in low level mode. 2.2.5 designing an ultra2 scsi system since ultra2 scsi is based on existing scsi standards, it can use existing driver programs as long as the software is able to negotiate for ultra2 scsi synchronous transfer rates. additional software modi?cations may be needed to take advantage of the new features in the SYM53C896. in the area of hardware, lvd scsi is required to achieve ultra2 scsi transfer rates and to support the longer cable and additional devices on the bus. all devices on the bus must have lvd scsi capabilities to guarantee ultra2 scsi transfer rates. for additional information on ultra2 scsi, refer to the spi-2 working document which is available from the scsi bbs referenced at the beginning of this manual. chapter 6, specifications contains ultra2 scsi timing information. in addition to the guidelines in the draft standard, make the following software and hardware adjustments to accommodate ultra2 scsi transfers: set the ultra enable bit to enable ultra2 scsi transfers. set the tolerant enable bit, bit 7 in the scsi test three (stest3) register, whenever the ultra enable bit is set. do not extend the sreq/sack ?ltering period with the scsi test two (stest2) register bit 1. when the ultra enable bit is set, the ?ltering period will be ?xed at 8 ns for ultra2 scsi or 15 ns for ultra scsi, regardless of the value of the sreq/sack ?ltering bit. use the scsi clock quadrupler.
2-22 functional description 2.2.5.1 using the scsi clock quadrupler the SYM53C896 can quadruple the frequency of a 40 mhz scsi clock, allowing the system to perform ultra2 scsi transfers. this option is user selectable with bit settings in the scsi test one (stest1) , scsi test three (stest3) , and scsi control three (scntl3) registers. at power-on or reset, the quadrupler is disabled and powered down. follow these steps to use the clock quadrupler: 1. set the sclk quadrupler enable bit ( scsi test one (stest1) register, bit 3). 2. poll bit 5 of the scsi test four (stest4) register. the SYM53C896 sets this bit as soon as it locks in the 160 mhz frequency. the frequency lockin takes approximately 100 microseconds. 3. halt the scsi clock by setting the halt scsi clock bit ( scsi test three (stest3) register, bit 5). 4. set the clock conversion factor using the scf and ccf ?elds in the scsi control three (scntl3) register. 5. set the sclk quadrupler select bit ( scsi test one (stest1) , bit 2). 6. clear the halt scsi clock bit. 2.2.6 prefetching scripts instructions when enabled by setting the prefetch enable bit (bit 5) in the dma control (dcntl) register, the prefetch logic in the SYM53C896 fetches 8 dwords of instruction. the prefetch logic automatically determines the maximum burst size that it can perform, based on the burst length as determined by the values in the dma mode (dmode) register. if the unit cannot perform bursts of at least four dwords, it disables itself. while the chip is prefetching scripts instructions, it will use pci cache commands memory read line, and memory read multiple, if pci caching is enabled. note: this feature is only useful when fetching scripts instructions from main memory. due to the short access time of scripts ram, prefetching is not necessary when fetching instructions from this memory. the SYM53C896 may ?ush the contents of the prefetch unit under certain conditions to ensure that the chip always operates from the most current version of the scripts instruction. when one of these
scsi functional description 2-23 conditions applies, the contents of the prefetch unit are automatically ?ushed. on every memory move instruction. the memory move instruction is often used to place modi?ed code directly into memory. to make sure that the chip executes all recent modi?cations, the prefetch unit ?ushes its contents and loads the modi?ed code every time an instruction is issued. to avoid inadvertently ?ushing the prefetch unit contents, use the no flush option for all memory move operations that do not modify code within the next 8 dwords. for more information on this instruction refer to chapter 5, scsi scripts instruction set . on every store instruction. the store instruction may also be used to place modi?ed code directly into memory. to avoid inadvertently ?ushing the prefetch unit contents use the no flush option for all store operations that do not modify code within the next 8 dwords. on every write to the dma scripts pointer (dsp) register. on all transfer control instructions when the transfer conditions are met. this is necessary because the next instruction to execute is not the sequential next instruction in the prefetch unit. when the prefetch flush bit ( dma control (dcntl) register, bit 6) is set. the unit ?ushes whenever this bit is set. the bit is self-clearing. 2.2.7 opcode fetch burst capability setting the burst opcode fetch enable bit (bit 1) in the dma mode (dmode) register (0x38) causes the SYM53C896 to burst in the ?rst two dwords of all instruction fetches. if the instruction is a memory-to- memory move, the third dword is accessed in a separate ownership. if the instruction is an indirect type, the additional dword is accessed in a subsequent bus ownership. if the instruction is a table indirect block move, the chip uses two accesses to obtain the four dwords required, in two bursts of two dwords each. note: this feature is only useful if prefetching is disabled. this feature is only useful if fetching scripts instructions from main memory. due to the short access time of scripts ram, burst opcode fetching is not necessary when fetching instructions from this memory.
2-24 functional description 2.2.8 load/store instructions the SYM53C896 supports the load/store instruction type, which simpli?es the movement of data between memory and the internal chip registers. it also enables the chip to transfer bytes to addresses relative to the data structure address (dsa) register. load/store data transfers to or from the scripts ram will remain internal to the chip and will not generate pci bus cycles. while a load/store to or from scripts ram is occurring, any external pci slave cycles that occur will be retried on the pci bus. this feature can be disabled by setting the dils bit in the chip control 0 (ccntl0) register. for more information on the load/store instructions refer to chapter 5, scsi scripts instruction set . 2.2.9 jtag boundary scan testing the SYM53C896 includes support for jtag boundary scan testing in accordance with the ieee 1149.1 speci?cation with one exception, which is explained in this section. this device accepts all required boundary scan instructions including the optional clamp, high-z, and idcode instructions. the SYM53C896 uses an 8-bit instruction register to support all boundary scan instructions. the data registers included in the device are the boundary data register, the idcode register, and the bypass register. this device can handle a 10 mhz tck frequency for tdo and tdi. due to design constraints, the rst/ pin (system reset) always 3-states the scsi pins when it is asserted. boundary scan logic does not control this action, and this is not compliant with the speci?cation. there are two solutions that resolve this issue: 1. use the rst/ pin as a boundary scan compliance pin. when the pin is deasserted, the device is boundary scan compliant and when asserted, the device is noncompliant. to maintain compliance the rst/ pin must be driven high. 2. when rst/ is asserted during boundary scan testing the expected output on the scsi pins must be the high-z condition, and not what is contained in the boundary scan data registers for the scsi pin output cells.
scsi functional description 2-25 2.2.10 scsi loopback mode the SYM53C896 loopback mode allows testing of both initiator and target functions and, in effect, lets the chip communicate with itself. when the loopback enable bit is set in the scsi test two (stest2) register, bit 4, the SYM53C896 allows control of all scsi signals whether the chip is operating in the initiator or target mode. for more information on this mode of operation refer to the lsi logic symbios ? pci to scsi i/o processors programming guide . 2.2.11 parity options the SYM53C896 implements a ?exible parity scheme that allows control of the parity sense, allows parity checking to be turned on or off, and has the ability to deliberately send a byte with bad parity over the scsi bus to test parity error recovery procedures. table 2.3 de?nes the bits that are involved in parity control and observation. table 2.4 describes the parity control function of the enable parity checking and assert scsi even parity bits in the scsi control one (scntl1) register, bit 2. table 2.5 describes the options available when a parity error occurs. figure 2.2 shows where parity checking is done in the SYM53C896.
2-26 functional description table 2.3 bits used for parity control and generation bit name location description assert satn/ on parity errors scsi control zero (scntl0) , bit 1 causes the SYM53C896 to automatically assert satn/ when it detects a scsi parity error while operating as an initiator. enable parity checking scsi control zero (scntl0) , bit 3 enables the SYM53C896 to check for parity errors. the SYM53C896 checks for odd parity. assert even scsi parity scsi control one (scntl1) , bit 2 determines the scsi parity sense generated by the SYM53C896 to the scsi bus. disable halt on satn/ or a parity error (target mode only) scsi control one (scntl1) , bit 5 causes the SYM53C896 not to halt operations when a parity error is detected in target mode. enable parity error interrupt scsi interrupt enable zero (sien0) , bit 0 determines whether the SYM53C896 generates an interrupt when it detects a scsi parity error. parity error scsi interrupt status zero (sist0) , bit 0 this status bit is set whenever the SYM53C896 detects a parity error on the scsi bus. status of scsi parity signal scsi status zero (sstat0) , bit 0 this status bit represents the active high current state of the scsi sdp0 parity signal. scsi sdp1 signal scsi status two (sstat2) , bit 0 this bit represents the active high current state of the scsi sdp1 parity signal. latched scsi parity scsi status two (sstat2) , bit 3 scsi status one (sstat1) , bit 3 these bits re?ect the scsi odd parity signal corresponding to the data latched into the scsi input data latch (sidl) register. master parity error enable chip test four (ctest4) , bit 3 enables parity checking during pci master data phases. master data parity error dma status (dstat) , bit 6 set when the SYM53C896, as a pci master, detects a target device signaling a parity error during a data phase. master data parity error interrupt enable dma interrupt enable (dien) , bit 6 by clearing this bit, a master data parity error does not cause assertion of inta/ (or intb/), but the status bit is set in the dma status (dstat) register.
scsi functional description 2-27 table 2.4 scsi parity control epc 1 1. epc = enable parity checking (bit 3 scsi control zero (scntl0) ). asep 2 2. asep = assert scsi even parity (bit 2 scsi control one (scntl1) ). description 0 0 does not check for parity errors. parity is generated when sending scsi data. asserts odd parity when sending scsi data. 0 1 does not check for parity errors. parity is generated when sending scsi data. asserts even parity when sending scsi data. 1 0 checks for odd parity on scsi data received. parity is generated when sending scsi data. asserts odd parity when sending scsi data. 1 1 checks for odd parity on scsi data received. parity is generated when sending scsi data. asserts even parity when sending scsi data. table 2.5 scsi parity errors and interrupts dhp 1 1. dhp = disable halt on satn/ or parity error (bit 5 scsi control one (scntl1) ). pa r 2 2. par = parity error (bit 0 scsi interrupt enable one (sien1) ). description 0 0 halts when a parity error occurs in the target or initiator mode and does not generate an interrupt. 0 1 halts when a parity error occurs in the target mode and generates an interrupt in the target or initiator mode. 1 0 does not halt in target mode when a parity error occurs until the end of the transfer. an interrupt is not generated. 1 1 does not halt in target mode when a parity error occurs until the end of the transfer. an interrupt is generated.
2-28 functional description figure 2.2 parity checking/generation 2.2.12 dma fifo the dma fifo is 8 bytes wide by 118 transfers deep. the dma fifo is illustrated in figure 2.3 . the default dma fifo size is 112 bytes to assure compatibility with older products in the sym53c8xx family. the dma fifo size may be set to 944 bytes by setting the dma fifo size bit, bit 5, in the chip test five (ctest5) register. pci interface** dma fifo* (64 bits x 118) sodl register* scsi interface** x s pci interface** dma fifo* (64 bits x 118) sidl register* scsi interface** g x pci interface** dma fifo* (64 bits x 118) sodl register* scsi interface** x s sodr register* pci interface** dma fifo* (64 bits x 118) scsi interface** g x scsi fifo* (8 or 16 bits x 31) x * = no parity protection ** = parity protected asynchronous scsi send asynchronous scsi receive synchronous scsi send synchronous scsi receive x - check parity g - generate 32-bit even pci parity s - generate 8-bit odd scsi parity
scsi functional description 2-29 figure 2.3 dma fifo sections the SYM53C896 supports 64-bit memory and automatically supports misaligned dma transfers. a 944-byte fifo allows the SYM53C896 to support 2, 4, 8, 16, 32, 64, or 128 dword bursts across the pci bus interface. 2.2.12.1 data paths the data path through the SYM53C896 is dependent on whether data is being moved into or out of the chip, and whether scsi data is being transferred asynchronously or synchronously. figure 2.4 shows how data is moved to/from the scsi bus in each of the different modes. the following items determine if any bytes remain in the data path when the chip halts an operation: asynchronous scsi send C step 1. if the dma fifo size is set to 112 bytes (bit 5 of the chip test five (ctest5) register cleared), look at the dma fifo (dfifo) and dma byte counter (dbc) registers and calculate if there are bytes left in the dma fifo. to make this calculation, subtract the seven least signi?cant bits of the dbc register from 118 transfers deep . . . . . . 8 bytes wide 8 bits byte lane 7 8 bits byte lane 6 8 bits byte lane 5 8 bits byte lane 4 8 bits byte lane 3 8 bits byte lane 2 8 bits byte lane 1 8 bits byte lane 0
2-30 functional description the 7-bit value of the dfifo register. and the result with 0x7f for a byte count between zero and 112. if the dma fifo size is set to 944 bytes (bit 5 of the chip test five (ctest5) register is set), subtract the 10 least signi?cant bits of the dma byte counter (dbc) register from the 10-bit value of the dma fifo byte offset counter, which consists of bits [1:0] in the chip test five (ctest5) register and bits [7:0] of the dma fifo (dfifo) register. and the result with 0x3ff for a byte count between zero and 944. step 2. read bit 5 in the scsi status zero (sstat0) and scsi status two (sstat2) registers to determine if any bytes are left in the scsi output data latch (sodl) register. if bit 5 is set in the sstat0 or sstat2 register, then the least signi?cant byte or the most signi?cant byte in the sodl register is full. checking this bit also reveals bytes left in the sodl register from a chained move operation with an odd byte count. synchronous scsi send C step 1. if the dma fifo size is set to 112 bytes (bit 5 of the chip test five (ctest5) register cleared), look at the dma fifo (dfifo) and dma byte counter (dbc) registers and calculate if there are bytes left in the dma fifo. to make this calculation, subtract the seven least signi?cant bits of the dbc register from the 7-bit value of the dfifo register. and the result with 0x7f for a byte count between zero and 112. if the dma fifo size is set to 944 bytes (bit 5 of the chip test five (ctest5) register is set), subtract the 10 least signi?cant bits of the dma byte counter (dbc) register from the 10-bit value of the dma fifo byte offset counter, which consists of bits [1:0] in the chip test five (ctest5) register and bits [7:0] of the dma fifo (dfifo) register. and the result with 0x3ff for a byte count between zero and 944. step 2. read bit 5 in the scsi status zero (sstat0) and scsi status two (sstat2) registers to determine if any bytes are left in the sodl register. if bit 5 is set in the sstat0 or sstat2 register, then the least signi?cant byte or the most signi?cant byte in the scsi output data latch (sodl) register is full. checking this bit also reveals bytes left in the sodl register from a chained move operation with an odd byte count.
scsi functional description 2-31 step 3. read bit 6 in the scsi status zero (sstat0) and scsi status two (sstat2) registers to determine if any bytes are left in the sodr register (a hidden buffer register which is not accessible). if bit 6 is set in the sstat0 or sstat2 register, then the least signi?cant byte or the most signi?cant byte in the sodr register is full. asynchronous scsi receive C step 1. if the dma fifo size is set to 112 bytes (bit 5 of the chip test five (ctest5) register cleared), look at the dfifo and dma byte counter (dbc) registers and calculate if there are bytes left in the dma fifo. to make this calculation, subtract the seven least signi?cant bits of the dbc register from the 7-bit value of the dma fifo (dfifo) register. and the result with 0x7f for a byte count between zero and 112. if the dma fifo size is set to 944 bytes (bit 5 of the chip test five (ctest5) register is set), subtract the 10 least signi?cant bits of the dma byte counter (dbc) register from the 10-bit value of the dma fifo byte offset counter, which consists of bits [1:0] in the ctest5 register and bits [7:0] of the dma fifo (dfifo) register. and the result with 0x3ff for a byte count between zero and 944. step 2. read bit 7 in the scsi status zero (sstat0) and scsi status two (sstat2) registers to determine if any bytes are left in the scsi input data latch (sidl) register. if bit 7 is set in the sstat0 or sstat2 registers, then the least signi?cant byte or the most signi?cant byte is full. step 3. if any wide transfers have been performed using the chained move instruction, read the wide scsi receive bit ( scsi control two (scntl2) , bit 0) to determine whether a byte is left in the scsi wide residue (swide) register. synchronous scsi receive C step 1. if the dma fifo size is set to 112 bytes, subtract the seven least signi?cant bits of the dma byte counter (dbc) register from the 7-bit value of the dma fifo (dfifo) register. and the result with 0x7f for a byte count between zero and 112.
2-32 functional description if the dma fifo size is set to 944 bytes (bit 5 of the chip test five (ctest5) register is set), subtract the 10 least signi?cant bits of the dma byte counter (dbc) register from the 10-bit value of the dma fifo byte offset counter, which consists of bits [1:0] in the ctest5 register and bits [7:0] of the dma fifo (dfifo) register. and the result with 0x3ff for a byte count between zero and 944. step 2. read the scsi status one (sstat1) register and examine bits [7:4], the binary representation of the number of valid bytes in the scsi fifo, to determine if any bytes are left in the scsi fifo. step 3. if any wide transfers have been performed using the chained move instruction, read the wide scsi receive bit ( scsi control two (scntl2) , bit 0) to determine whether a byte is left in the scsi wide residue (swide) register. figure 2.4 SYM53C896 host interface scsi data paths 2.2.13 scsi bus interface the SYM53C896 performs se and lvd transfers, and supports traditional hvd operation when the chip is connected to external hvd transceivers. pci interface dma fifo (8 bytes x 118) sodl register scsi interface pci interface dma fifo (8 bytes x 118) sidl register scsi interface pci interface dma fifo (8 bytes x 118) sodl register scsi interface sodr register pci interface dma fifo (8 bytes x 118) scsi interface scsi fifo (1 or 2 bytes x 31) asynchronous scsi send asynchronous scsi receive synchronous scsi send synchronous scsi receive swide register swide register
scsi functional description 2-33 to support lvd scsi, all scsi data and control signals have both negative and positive signal lines. the negative signals perform the scsi data and control function. in the se mode they become virtual ground drivers. in the hvd mode, the positive signals provide directional control to the external transceivers. tolerant technology provides signal ?ltering at the inputs of sreq/ and sack/ to increase immunity to signal re?ections. 2.2.13.1 lvd link technology to support greater device connectivity and a longer scsi cable, the SYM53C896 features lvd link technology, the lsi logic implementation of lvd scsi. lvd link transceivers provide the inherent reliability of differential scsi, and a long-term migration path of faster scsi transfer rates. lvd link technology is based on current drive. its low output current reduces the power needed to drive the scsi bus, so that the i/o drivers can be integrated directly onto the chip. this reduces the cost and complexity compared to traditional hvd designs. lvd link lowers the amplitude of noise re?ections and allows higher transmission frequencies. the lsi logic lvd link transceivers operate in lvd or se modes. they allow the chip to detect a hvd signal when the chip is connected to external hvd transceivers. the SYM53C896 automatically detects which type of signal is connected, based on the voltage detected by the diffsens pin. bits 7 and 6 of the scsi test four (stest4) register contain the encoded value for the type of signal that is detected (lvd, se, or hvd). please see the scsi test four (stest4) register description for encoding and other bit information. 2.2.13.2 hvd mode to maintain backward compatibility with legacy systems, the SYM53C896 can operate in the hvd mode (when the chip is connected to external differential transceivers). in the hvd mode, the sd[15:0]+, sdp[1:0]+, sreq+, sack+, srst+, sbsy+, and ssel+ signals control the direction of external differential pair transceivers. the SYM53C896 is placed in the hvd mode by setting the dif bit, bit 5, of the scsi test two (stest2) register (0x4e). setting this bit 3-states the sbsy - , ssel - , and srst - pads so they can be used as pure input pins. in
2-34 functional description addition to the standard scsi lines, the signals shown in table 2.6 are used by the SYM53C896 during hvd operation. in the example differential wiring diagram in figure 2.5 , the SYM53C896 is connected to ti sn75976 differential transceivers for ultra scsi operation. the recommended value of the pull-up resistor on the sreq - ,sack - , smsg - , sc_d - , si_o - ,satn - , sd[7:0] - , and sdp0 - lines is 680 w when the active negation portion of lsi logic tolerant technology is not enabled. when tolerant technology is enabled, the recommended resistor value on the sreq - ,sack - , sd[7:0] - , and sdp0 - signals is 1.5 k w . the electrical characteristics of these pins change when tolerant technology is enabled, permitting a higher resistor value. to interface the SYM53C896 to the sn75976a, connect the positive pins in the scsi lvd pair of the SYM53C896 directly to the transceiver enables (de/re/). these signals control the direction of the channels on the sn75976a. the scsi bidirectional control and data pins (sd[7:0] - , sdp0 - , sreq -, sack - , smsg - , si_o - , sc_d - , and satn - ) of the SYM53C896 connect to the bidirectional data pins (na) of the sn75976a with a pull-up resistor. the pull-up value should be no lower than the transceiver i ol can tolerate, but not so high as to cause rc timing problems. the three remaining pins, ssel - , sbsy - and srst - , are connected to the sn75976a with a pull-down resistor. the pull-down resistors are required table 2.6 hvd signals signal function sbsy+, ssel+, srst+ active high signals used to enable the differential drivers as outputs for scsi signals sbsy - , ssel - , and srst - , respectively. sd[15:0]+, sdp[1:0]+ active high signals used to control the direction of the differential drivers for scsi data and parity lines, respectively. sack+ active high signal used to control the direction of the differential drivers for the initiator group signals satn - and sack - . sreq+ active high signal used to control the direction of the differential drivers for target group signals smsg - , sc_d - , si_o - and sreq - . diffsens input to the SYM53C896 used to detect the voltage level of a scsi signal to determine whether it is a se, lvd, or hvd signal. the encoded result is displayed in scsi test four (stest4) bits 7 and 6.
scsi functional description 2-35 when the pins (na) of the sn75976a are con?gured as inputs. when the data pins are inputs, the resistors provide a bias voltage to both the SYM53C896 pins (ssel - , sbsy - , and srst - ) and the sn75976a data pins. because the ssel - , sbsy - , and srst - pins on the SYM53C896 are inputs only, this con?guration allows for the ssel - , sbsy - , and srst - scsi signals to be asserted on the scsi bus. the differential pairs on the scsi bus are reversed when connected to the sn75976a due to the active low nature of the scsi bus. 8-bit/16-bit scsi and the hvd interface C in an 8-bit scsi bus, the sd[15:8] pins on the SYM53C896 should be pulled up with a 1.5 k w resistor or terminated like the rest of the scsi bus lines. this is very important, as errors may occur during reselection if these lines are left ?oating.
2-36 functional description figure 2.5 8-bit hvd wiring diagram for ultra scsi sym53c8xx sel+ bsy+ rst+ sel - bsy - rst - req - ack - msg - c/d - i/o - at n - req + ack+ sd[8:15]+ sdp1+ sd[8:15] - sdp1 - sdp0+ sd7+ sd6+ sd5+ sd4+ sd3+ sd2+ sd1+ sd0+ sdp0 - sd7 - sd6 - sd5 - sd4 - sd3 - sd2 - sd1 - sd0 - diffsens 1.5 k 1.5 k vdd vdd 1.5 k 1.5 k vdd 1.5 k 1.5 k 1.5 k float float vdd 1.5 k vdd 1.5 k sn75976a2 cde0 cde1 cde2 bsr cre 1a 1de/re 2a 2de/re 4a 4de/re 5a 5de/re 6a 6de/re 7a 7de/re 8a 8de/re 9a 9de/re 3a 3de/re sel- sel+ bsy+ rst+ req/ bsy- rst- ack - msg - c_d - i_o - atn- vdd 1.5 k diffsens schottky diode diffsens (pin 21) - sel scsi bus +sel - bsy +bsy - rst (42) +rst - req +req - ack +ack - msg +msg - c/d +c/d - i/o +i/o - at n +atn 1b+ 1b - 2b+ 2b - 3b+ 3b - 4b+ 4b - 5b+ 5b - 6b+ 6b - 7b+ 7b - 8b+ 8b - 9b+ 9b - (41) (34) (33) (38) (37) (46) (45) (36) (35) (40) (39) (44) (43) (48) (47) (30) (29) sn75976a2 cde0 cde1 cde2 bsr cre 1a 1de/re 2a 2de/re 4a 4de/re 5a 5de/re 6a 6de/re 7a 7de/re 8a 8de/re 9a 9de/re 3a 3de/re - db0 +db0 - db1 +db1 - db2 (4) +db2 - db3 +db3 - db4 +db4 - db5 +db5 - db6 +db6 - db7 +db7 - dbp +dbp 1b+ 1b - 2b+ 2b - 3b+ 3b - 4b+ 4b - 5b+ 5b - 6b+ 6b - 7b+ 7b - 8b+ 8b - 9b+ 9b - (3) (6) (5) (8) (7) (10) (9) (12) (11) (14) (13) (16) (15) (18) (17) (20) (19) diffsens diffsens sd0+ sd1+ sd2+ sd3+ sd4+ sd5+ sd6+ sd7+ sdp0+ sd0 - sd1 - sd2 - sd3 - sd4 - sd5 - sd6 - sd7 - sdp0 - 1.5 k
scsi functional description 2-37 2.2.13.3 scsi termination the terminator networks provide the biasing needed to pull signals to an inactive voltage level, and to match the impedance seen at the end of the cable with the characteristic impedance of the cable. terminators must be installed at the extreme ends of the scsi chain, and only at the ends. no system should ever have more or less than two terminators installed and active. scsi host adapters should provide a means of accommodating terminators. there should be a means of disabling the termination. se cables can use a 220 w pull-up resistor to the terminator power supply (term power) line and a 330 w pull-down resistor to ground. because of the high-performance nature of the SYM53C896, regulated (or active) termination is recommended. figure 2.6 shows a unitrode active terminator. tolerant technology active negation can be used with either termination network. for information on terminators that support lvd, refer to the spi-2 draft standard. note: if the SYM53C896 is to be used in a design with only an 8-bit scsi bus, all 16 data lines must be terminated.
2-38 functional description figure 2.6 regulated termination for ultra2 scsi 2.2.14 select/reselect during selection/reselection in multithreaded scsi i/o environments, it is not uncommon to be selected or reselected while trying to perform selection/reselection. this situation may occur when a scsi controller (operating in the initiator mode) tries to select a target and is reselected by another. the select scripts instruction has an alternate address to which the scripts will jump when this situation occurs. the analogous situation for target devices is being selected while trying to perform a reselection. once a change in operating mode occurs, the initiator scripts should start with a set initiator instruction or the target scripts should start with a set target instruction. the selection and reselection enable bits ( scsi chip id (scid) bits 5 and 6, respectively) should both be asserted ucc5630 4 5 6 7 11 12 13 14 15 16 17 line1+ line1 - line2+ line2 - line3+ line3 - line4+ line4 - line5+ line5 - discnct line9 - line9+ line8 - line8+ line7 - line7+ line6 - line6+ se lv d hvd diffsens diff b 32 31 30 29 25 24 23 22 33 34 35 20 21 0.1 m f to led drivers sdp0 - sdp0+ sd7 - sd7+ sd6 - sd6+ sd5 - sd5+ sd0+ sd0 - sd1+ sd1 - sd2+ sd2 - sd3+ sd3 - sd4+ sd4 - 22 k diffsens connects to the scsi bus diffsens line to detect what type of devices (se, lvd, or hvd) are connected to the scsi bus. discnct shuts down the terminator when it is not at the end of the bus. the disconnect pin low enables the terminator. *use additional ucc5630 terminators to terminate the scsi control signals and wide scsi data byte as needed.
scsi functional description 2-39 so that the SYM53C896 may respond as an initiator or as a target. if only selection is enabled, the SYM53C896 cannot be reselected as an initiator. there are also status and interrupt bits in the scsi interrupt status zero (sist0) and scsi interrupt enable zero (sien0) registers, respectively, indicating that the SYM53C896 has been selected (bit 5) and reselected (bit 4). 2.2.15 synchronous operation the SYM53C896 can transfer synchronous scsi data in both the initiator and target modes. the scsi transfer (sxfer) register controls both the synchronous offset and the transfer period. it may be loaded by the cpu before scripts execution begins, from within scripts using a table indirect i/o instruction, or with a read-modify-write instruction. the SYM53C896 can receive data from the scsi bus at a synchronous transfer period as short as 25 ns, regardless of the transfer period used to send data. the SYM53C896 can receive data at one-fourth of the divided sclk frequency. depending on the sclk frequency, the negotiated transfer period, and the synchronous clock divider, the SYM53C896 can send synchronous data at intervals as short as 25 ns for ultra2 scsi, 50 ns for ultra scsi, 100 ns for fast scsi and 200 ns for scsi-1. 2.2.15.1 determining the data transfer rate synchronous data transfer rates are controlled by bits in two different registers of the SYM53C896. following is a brief description of the bits. figure 2.7 illustrates the clock division factors used in each register, and the role of the register bits in determining the transfer rate. 2.2.15.2 scsi control three (scntl3) register, bits [6:4] (scf[2:0]) the scf[2:0] bits select the factor by which the frequency of sclk is divided before being presented to the synchronous scsi control logic. the output from this divider controls the rate at which data can be received. this rate must not exceed 160 mhz. the receive rate of synchronous scsi data is one-fourth of the scf divider output. for example, if sclk is 160 mhz and the scf value is set to divide by one, then the maximum rate at which data can be received is 40 mhz (160/(1*4) = 40).
2-40 functional description 2.2.15.3 scsi control three (scntl3) register, bits [2:0] (ccf[2:0]) the ccf[2:0] bits select the factor by which the frequency of sclk is divided before being presented to the asynchronous scsi core logic. this divider must be set according to the input clock frequency in the table. 2.2.15.4 scsi transfer (sxfer) register, bits [7:5] (tp[2:0]) the tp[2:0] divider bits determine the scsi synchronous transfer period when sending synchronous scsi data in either the initiator or target mode. this value further divides the output from the scf divider. 2.2.15.5 ultra2 scsi synchronous data transfers ultra2 scsi is an extension of the current ultra scsi synchronous transfer speci?cations. it allows synchronous transfer periods to be negotiated down as low as 25 ns, which is half the 50 ns period allowed under ultra scsi. this will allow a maximum transfer rate of 80 mbytes/s on a 16-bit, lvd scsi bus. the SYM53C896 has a scsi clock quadrupler that must be enabled for the chip to perform ultra2 scsi transfers with a 40 mhz oscillator. in addition, the following bit values affect the chips ability to support ultra2 scsi synchronous transfer rates: clock conversion factor bits, scsi control three (scntl3) register bits [2:0] and synchronous clock conversion factor bits, scntl3 register bits [6:4]. these ?elds support a value of 111 (binary), allowing the 160 mhz sclk frequency to be divided down by 8 for the asynchronous logic. ultra2 scsi enable bit, scsi control three (scntl3) register bit 7. setting this bit enables ultra2 scsi synchronous transfers in systems that use the internal scsi clock quadrupler. tolerant enable bit, scsi test three (stest3) register bit 7. active negation must be enabled for the SYM53C896 to perform ultra2 scsi transfers. note: the clock quadrupler requires a 40 mhz external clock. lsi logic symbios software assumes that the SYM53C896 is connected to a 40 mhz external clock, which is quadrupled to achieve ultra2 scsi transfer rates.
scsi functional description 2-41 figure 2.7 determining the synchronous transfer rate 2.2.16 interrupt handling the scripts processors in the SYM53C896 perform most functions independently of the host microprocessor. however, certain interrupt situations must be handled by the external microprocessor. this section explains all aspects of interrupts as they apply to the SYM53C896. 2.2.16.1 polling and hardware interrupts the external microprocessor is informed of an interrupt condition by polling or hardware interrupts. polling means that the microprocessor must continually loop and read a register until it detects a bit that is set indicating an interrupt. this method is the fastest, but it wastes cpu time sclk clock quadrupler qclk scf divider ccf divider synchronous divider asynchronous scsi logic divide by 4 scf2 scf1 scf0 scf divisor 0011 0 1 0 1.5 0112 1003 0003 1014 1106 1118 tp2 tp1 tp0 xferp divisor 0004 0015 0106 0117 1008 1019 11010 11111 ccf2 ccf1 ccf0 divisor qclk (mhz) 0 0 1 1 50.1C66.00 0 1 0 1.5 16.67C25.00 0 1 1 2 25.1C37.50 1 0 0 3 37.51C50.00 0 0 0 3 50.01C66.00 1 0 1 4 75.01C80.00 1 1 0 6 120 1 1 1 8 160 example: qclk (quadrupled scsi clock) = 160 mhz scf = 1 (/1), xferp = 0 (/4), ccf = 7 (/8) synchronous send rate = (qclk/scf)/xferp = (160/1) /4 = 40 mbytes/s synchronous receive rate = (qclk/scf) /4 = (160/1) /4 = 40 mbytes/s this point must not exceed 160 mhz receive clock send clock (to scsi bus)
2-42 functional description that could be used for other system tasks. the preferred method of detecting interrupts in most systems is hardware interrupts. in this case, the SYM53C896 asserts the interrupt request (inta/ or intb/) line that interrupts the microprocessor, causing the microprocessor to execute an interrupt service routine. a hybrid approach would use hardware interrupts for long waits, and use polling for short waits. scsi function a is routed to pci interrupt inta/. scsi function b is normally routed to intb/, but can be routed to inta/ if a pull-up is connected to mad[4]. see section 3.7, mad bus programming for additional information. 2.2.16.2 registers the registers in the SYM53C896 that are used for detecting or de?ning interrupts are is tat, scsi interrupt status zero (sist0) , scsi interrupt status one (sist1) , scsi interrupt enable zero (sien0) , scsi interrupt enable one (sien1) , dma control (dcntl) , and dma interrupt enable (dien) . istat C the istat register includes the interrupt status zero (istat0) , interrupt status one (istat1) , mailbox zero (mbox0) , and mailbox one (mbox1) registers. it is the only register that can be accessed as a slave during the scripts operation. therefore, it is the register that is polled when polled interrupts are used. it is also the ?rst register that should be read after the inta/ (or intb/) pin is asserted in association with a hardware interrupt. the intf (interrupt-on-the-fly) bit should be the ?rst interrupt serviced. it must be written to one to be cleared. this interrupt must be cleared before servicing any other interrupts. see register 0x14, interrupt status zero (istat0) , bit 5 signal process in chapter 4, registers for additional information. the host (c code) or the scripts code could potentially try to access the mailbox bits at the same time. if the sip bit in the interrupt status zero (istat0) register is set, then a scsi-type interrupt has occurred and the scsi interrupt status zero (sist0) and scsi interrupt status one (sist1) registers should be read. if the dip bit in the interrupt status zero (istat0) register is set, then a dma-type interrupt has occurred and the dma status (dstat) register should be read.
scsi functional description 2-43 scsi-type and dma-type interrupts may occur simultaneously, so in some cases both sip and dip may be set. sist0 and sist1 C the scsi interrupt status zero (sist0) and scsi interrupt status one (sist1) registers contain scsi-type interrupt bits. reading these registers determines which condition or conditions caused the scsi-type interrupt, and clears that scsi interrupt condition. if the SYM53C896 is receiving data from the scsi bus and a fatal interrupt condition occurs, the chip attempts to send the contents of the dma fifo to memory before generating the interrupt. if the SYM53C896 is sending data to the scsi bus and a fatal scsi interrupt condition occurs, data could be left in the dma fifo. because of this the dma fifo empty (dfe) bit in dma status (dstat) should be checked. if this bit is cleared, set the clf (clear dma fifo) and csf (clear scsi fifo) bits before continuing. the clf bit is bit 2 in chip test three (ctest3) . the csf bit is bit 1 in scsi test three (stest3) . dstat C the dma status (dstat) register contains the dma-type interrupt bits. reading this register determines which condition or conditions caused the dma-type interrupt, and clears that dma interrupt condition. bit 7 in ds tat, dfe, is purely a status bit; it will not generate an interrupt under any circumstances and will not be cleared when read. dma interrupts ?ush neither the dma nor scsi fifos before generating the interrupt, so the dfe bit in the dstat register should be checked after any dma interrupt. if the dfe bit is cleared, then the fifos must be cleared by setting the clf (clear dma fifo) and csf (clear scsi fifo) bits, or ?ushed by setting the flf (flush dma fifo) bit. sien0 and sien1 C the scsi interrupt enable zero (sien0) and scsi interrupt enable one (sien1) registers are the interrupt enable registers for the scsi interrupts in scsi interrupt status zero (sist0) and scsi interrupt status one (sist1) . dien C the dma interrupt enable (dien) register is the interrupt enable register for dma interrupts in dma status (dstat) .
2-44 functional description dma control (dcntl) C when bit 1 in this register is set, the inta/ (or intb/) pin is not asserted when an interrupt condition occurs. the interrupt is not lost or ignored, but is merely masked at the pin. clearing this bit when an interrupt is pending immediately causes the inta/ (or intb/) pin to assert. as with any register other than is tat, this register cannot be accessed except by a scripts instruction during scripts execution. 2.2.16.3 fatal vs. nonfatal interrupts a fatal interrupt, as the name implies, always causes the scripts to stop running. all nonfatal interrupts become fatal when they are enabled by setting the appropriate interrupt enable bit. interrupt masking is discussed in section 2.2.16.4, masking . all dma interrupts (indicated by the dip bit in interrupt status zero (istat0) and one or more bits in dma status (dstat) being set) are fatal. some scsi interrupts (indicated by the sip bit in the interrupt status zero (istat0) and one or more bits in scsi interrupt status zero (sist0) or scsi interrupt status one (sist1) being set) are nonfatal. when the SYM53C896 is operating in the initiator mode, only the function complete (cmp), selected (sel), reselected (rsl), general purpose timer expired (gen), and handshake-to-handshake timer expired (hth) interrupts are nonfatal. when operating in the target mode, cmp, sel, rsl, target mode: satn/ active (m/a), gen, and hth are nonfatal. refer to the description for the disable halt on a parity error or satn/ active (target mode only) (dhp) bit in the scsi control one (scntl1) register to con?gure the chips behavior when the satn/ interrupt is enabled during target mode operation. the interrupt-on-the-fly interrupt is also nonfatal, since scripts can continue when it occurs. the reason for nonfatal interrupts is to prevent the scripts from stopping when an interrupt occurs that does not require service from the cpu. this prevents an interrupt when arbitration is complete (cmp set), when the SYM53C896 is selected or reselected (sel or rsl set), when the initiator asserts atn (target mode: satn/ active), or when the general purpose or handshake-to-handshake timers expire. these interrupts are not needed for events that occur during high-level scripts operation.
scsi functional description 2-45 2.2.16.4 masking masking an interrupt means disabling or ignoring that interrupt. interrupts can be masked by clearing bits in the scsi interrupt enable zero (sien0) and scsi interrupt enable one (sien1) (for scsi interrupts) registers or dma interrupt enable (dien) (for dma interrupts) register. how the chip responds to masked interrupts depends on: whether polling or hardware interrupts are being used; whether the interrupt is fatal or nonfatal; and whether the chip is operating in the initiator or target mode. if a nonfatal interrupt is masked and that condition occurs, the scripts do not stop, the appropriate bit in the scsi interrupt status zero (sist0) or scsi interrupt status one (sist1) is still set, the sip bit in the interrupt status zero (istat0) is not set, and the inta/ (or intb/) pin is not asserted. if a fatal interrupt is masked and that condition occurs, then the scripts still stop, the appropriate bit in the dma status (dstat) , scsi interrupt status zero (sist0) ,or scsi interrupt status one (sist1) register is set, and the sip or dip bit in the interrupt status zero (istat0) register is set, but the inta/ (or intb/) pin is not asserted. interrupts can be disabled by setting the sync_irqd bit in the interrupt status one (istat1) register. if an interrupt is already asserted and sync_irqd is then set, the interrupt will remain until serviced. further interrupts will be blocked. when the SYM53C896 is initialized, enable all fatal interrupts if hardware interrupts are being used. if a fatal interrupt is disabled and that interrupt condition occurs, the scripts halts and the system never knows it unless it times out and checks the interrupt status zero (istat0) , interrupt status one (istat1) , mailbox zero (mbox0) , and mailbox one (mbox1) registers after a certain period of inactivity. if istat is being polled instead of using hardware interrupts, then masking a fatal interrupt makes no difference since the sip and dip bits in the interrupt status zero (istat0) inform the system of interrupts, not the inta/ (or intb/) pin. masking an interrupt after inta/ (or intb/) is asserted does not cause deassertion of inta/ (or intb/).
2-46 functional description 2.2.16.5 stacked interrupts the SYM53C896 will stack interrupts, if they occur, one after the other. if the sip or dip bits in the interrupt status zero (istat0) register are set (?rst level), then there is already at least one pending interrupt, and any future interrupts are stacked in extra registers behind the scsi interrupt status zero (sist0) , scsi interrupt status one (sist1) , and dma status (dstat) registers (second level). when two interrupts have occurred and the two levels of the stack are full, any further interrupts set additional bits in the extra registers behind sist0, sist1, and dstat. when the ?rst level of interrupts are cleared, all the interrupts that came in afterward move into sist0, sist1, and ds tat. after the ?rst interrupt is cleared by reading the appropriate register, the inta/ (or intb/) pin is deasserted for a minimum of three clks; the stacked interrupts move into sist0, sist1, or dstat; and the inta/ (or intb/) pin is asserted once again. since a masked nonfatal interrupt does not set the sip or dip bits, interrupt stacking does not occur. a masked, nonfatal interrupt still posts the interrupt in scsi interrupt status zero (sist0) , but does not assert the inta/ (or intb/) pin. since no interrupt is generated, future interrupts move into sist0 or scsi interrupt status one (sist1) instead of being stacked behind another interrupt. when another condition occurs that generates an interrupt, the bit corresponding to the earlier masked nonfatal interrupt is still set. a related situation to interrupt stacking is when two interrupts occur simultaneously. since stacking does not occur until the sip or dip bits are set, there is a small timing window in which multiple interrupts can occur but are not stacked. these could be multiple scsi interrupts (sip set), multiple dma interrupts (dip set), or multiple scsi and multiple dma interrupts (both sip and dip set). as previously mentioned, dma interrupts do not attempt to ?ush the fifos before generating the interrupt. it is important to set either the clear dma fifo (clf) and clear scsi fifo (csf) bits if a dma interrupt occurs and the dma fifo empty (dfe) bit is not set. this is because any future scsi interrupts are not posted until the dma fifo is cleared of data. these locked out scsi interrupts are posted as soon as the dma fifo is empty.
scsi functional description 2-47 2.2.16.6 halting in an orderly fashion when an interrupt occurs, the SYM53C896 attempts to halt in an orderly fashion. if the interrupt occurs in the middle of an instruction fetch, the fetch is completed, except in the case of a bus fault. execution does not begin, but the dsp points to the next instruction since it is updated when the current instruction is fetched. if the dma direction is a write to memory and a scsi interrupt occurs, the SYM53C896 attempts to ?ush the dma fifo to memory before halting. under any other circumstances only the current cycle is completed before halting, so the dfe bit in dma status (dstat) should be checked to see if any data remains in the dma fifo. scsi sreq/sack handshakes that have begun are completed before halting. the SYM53C896 attempts to clean up any outstanding synchronous offset before halting. in the case of transfer control instructions, once instruction execution begins it continues to completion before halting. if the instruction is a jump/call when/if , the dma scripts pointer (dsp) is updated to the transfer address before halting. all other instructions may halt before completion. 2.2.16.7 sample interrupt service routine the following is a sample of an interrupt service routine for the SYM53C896. it can be repeated if polling is used, or should be called when the inta/ (or intb/) pin is asserted if hardware interrupts are used. 1. read interrupt status zero (istat0) . 2. if the intf bit is set, it must be written to a one to clear this status. 3. if only the sip bit is set, read scsi interrupt status zero (sist0) and scsi interrupt status one (sist1) to clear the scsi interrupt condition and get the scsi interrupt status. the bits in the sist0 and sist1 tell which scsi interrupts occurred and determine what action is required to service the interrupts.
2-48 functional description 4. if only the dip bit is set, read dma status (dstat) to clear the interrupt condition and get the dma interrupt status. the bits in dstat tell which dma interrupts occurred and determine what action is required to service the interrupts. 5. if both the sip and dip bits are set, read scsi interrupt status zero (sist0) , scsi interrupt status one (sist1) , and dma status (dstat) to clear the scsi and dma interrupt condition and get the interrupt status. if using 8-bit reads of the sist0, sist1, and dstat registers to clear interrupts, insert a 12 clock delay between the consecutive reads to ensure that the interrupts clear properly. both the scsi and dma interrupt conditions should be handled before leaving the interrupt service routine. it is recommended that the dma interrupt is serviced before the scsi interrupt, because a serious dma interrupt condition could in?uence how the scsi interrupt is acted upon. 6. when using polled interrupts go back to step 1 before leaving the interrupt service routine in case any stacked interrupts moved in when the ?rst interrupt was cleared. when using hardware interrupts, the inta/ (or intb/) pin is asserted again if there are any stacked interrupts. this should cause the system to re-enter the interrupt service routine. 2.2.17 interrupt routing this section documents the recommended approach to raid ready interrupt routing for the SYM53C896. in order to be compatible with ami raid upgrade products and the SYM53C896, the following requirements must be met: when a raid upgrade card is installed in the upgrade slot, interrupts from the motherboard scsi controller(s) assigned to the raid upgrade card must be routed to intc/ and intd/ of the upgrade slot and isolated from the motherboard interrupt controller. the system processor must not see interrupts from the scsi controllers that are to be serviced by the raid upgrade card. an upgrade slot is one that is connected to the interrupt routing logic for motherboard scsi device(s). when a pci raid upgrade board is installed into the system, it would be plugged into this slot if it is to control motherboard scsi device(s).
scsi functional description 2-49 the tdi pin of the upgrade slot must be connected to the int_dir/ pin of the SYM53C896. when a raid upgrade card is not installed, interrupts from a scsi core must not be presented to the systems interrupt controller using multiple interrupt inputs. figure 2.8 shows an example con?guration. in this example the SYM53C896 dual channel ultra2 scsi controller contains the interrupt routing logic. the SYM53C896 supports four different interrupt routing modes. additional information for these modes may be found in register 0x4d, scsi test one (stest1) description in chapter 4, registers . each scsi core within the chip may be con?gured independently. the interrupt routing mode is selected using bits [1:0] in the stest1 register within each core. mode 0 is the default mode and is compatible with ami raid upgrade products. if the implementation shown in figure 2.8 is used, intc/ and intd/ of the pci raid upgrade slot cannot be used when a non-raid upgrade card is installed in the slot. if this restriction is not acceptable, additional buffer logic must be implemented on the motherboard. as long as the interrupt routing requirements stated above are satis?ed, a motherboard designer could implement this design with external logic.
2-50 functional description figure 2.8 interrupt routing hardware using the SYM53C896 there can only be one entity controlling a motherboard scsi core or con?icts will occur. typically a scsi core will be controlled by the scsi bios and an operating system driver. when a scsi core is allocated to a raid adapter, however, a mechanism must be implemented to prevent the scsi bios and operating system driver from trying to access the scsi core. the motherboard designer has several options to choose from for doing this. the ?rst option is to have the scsi core load its pci subsystem id using a serial eprom on power-up. if bit 15 in this id is set, the lsi logic symbios bios and operating system drivers will ignore the chip. this makes it possible to control the assignment of the motherboard scsi cores using a con?guration utility. the second option is to provide motherboard and system bios support for nvs. the scsi core may then be enabled or disabled using the scsi bios con?guration utility. not all versions of the symbios drivers support this capability. a4 a6 a7 b8 b7 scsi core i scsi core ii SYM53C896 alt_inta/ 2.7 k + 5 v inta/ alt_intb/ intb/ 2.7 k + 5 v intb/ intd/ inta/ intc/ tdi + 5 v int_dir pci raid upgrade slot inta/ pci raid upgrade slot intb/ mb scsi inta/ mb scsi intb/ these interrupt lines are connected to the other pci slot interrupt lines as determined by the motherboard interrupt routing scheme. 10 k pci raid upgrade slot
scsi functional description 2-51 the third option is to have the system bios not report the existence of the scsi controller chips when the scsi bios and operating systems make pci bios calls. this approach requires modi?cations to the system bios and assumes the operating system uses pci bios calls when searching for pci devices. 2.2.18 chained block moves since the SYM53C896 has the capability to transfer 16-bit wide scsi data, a unique situation occurs when dealing with odd bytes. the chained move (chmov) scripts instruction along with the wide scsi send (wss) and wide scsi receive (wsr) bits in the scsi control two (scntl2) register are used to facilitate these situations. the chained block move instruction is illustrated in figure 2.9 . 2.2.18.1 wide scsi send bit the wss bit is set whenever the scsi controller is sending data (data-out for the initiator or data-in for the target) and the controller detects a partial transfer at the end of a chained block move scripts instruction (this ?ag is not set if a normal block move instruction is used). under this condition, the scsi controller does not send the low-order byte of the last partial memory transfer across the scsi bus. instead, the low-order byte is temporarily stored in the lower byte of the scsi output data latch (sodl) register and the wss ?ag is set. the hardware uses the wss ?ag to determine what behavior must occur at the start of the next data send transfer. when the wss ?ag is set at the start of the next transfer, the ?rst byte (the high-order byte) of the next data send transfer is married with the stored low-order byte in the sodl register; and the two bytes are sent out across the bus, regardless of the type of block move instruction (normal or chained). the ?ag is automatically cleared when the married word is sent. the ?ag is alternately cleared through scripts or by the microprocessor. also, the microprocessor or scripts can use this bit for error detection and recovery purposes. 2.2.18.2 wide scsi receive bit the wsr bit is set whenever the scsi controller is receiving data (data-in for the initiator or data-out for the target) and the controller detects a partial transfer at the end of a block move or chained block move scripts instruction. when wsr is set, the high-order byte of the
2-52 functional description last scsi bus transfer is not transferred to memory. instead, the byte is temporarily stored in the scsi wide residue (swide) register. the hardware uses the wsr bit to determine what behavior must occur at the start of the next data receive transfer. the bit is automatically cleared at the start of the next data receive transfer. the bit can alternatively be cleared by the microprocessor or through scripts. also, the microprocessor or scripts can use this bit for error detection and recovery purposes. 2.2.18.3 swide register this register is used to store data for partial byte data transfers. for receive data, the scsi wide residue (swide) register holds the high-order byte of a partial scsi transfer which has not yet been transferred to memory. this stored data may be a residue byte (and therefore ignored) or it may be valid data that is transferred to memory at the beginning of the next block move instruction. 2.2.18.4 sodl register for send data, the low-order byte of the scsi output data latch (sodl) register holds the low-order byte of a partial memory transfer which has not yet been transferred across the scsi bus. this stored data is usually married with the ?rst byte of the next data send transfer, and both bytes are sent across the scsi bus at the start of the next data send block move command. 2.2.18.5 chained block move scripts instruction a chained block move scripts instruction is primarily used to transfer consecutive data send or data receive blocks. using the chained block move instruction facilitates partial receive transfers and allows correct partial send behavior without additional opcode overhead. behavior of the chained block move instruction varies slightly for sending and receiving data. for receive data (data-in for the initiator or data-out for the target), a chained block move instruction indicates that if a partial transfer occurred at the end of the instruction, the wsr ?ag is set. the high-order byte of the last scsi transfer is stored in the scsi wide residue (swide) register rather than transferred to memory. the contents of the swide register should be the ?rst byte transferred to memory at the start of the
scsi functional description 2-53 chained block move data stream. since the byte count always represents data transfers to/from memory (as opposed to the scsi bus), the byte transferred out of the scsi wide residue (swide) register is one of the bytes in the byte count. if the wsr bit is cleared when a receive data chained block move instruction is executed, the data transfer occurs similar to that of the regular block move instruction. whether the wsr bit is set or cleared, when a normal block move instruction is executed, the contents of the swide register are ignored and the transfer takes place normally. for n consecutive wide data receive block move instructions, the 2nd through the nth block move instructions should be chained block moves. for send data (data-out for the initiator or data-in for the target), a chained block move instruction indicates that if a partial transfer terminates the chained block move instruction, the last low-order byte (the partial memory transfer) should be stored in the lower byte of the scsi output data latch (sodl) register and not sent across the scsi bus. without the chained block move instruction, the last low-order byte would be sent across the scsi bus. the starting byte count represents data bytes transferred from memory but not to the scsi bus when a partial transfer exists. for example, if the instruction is an initiator chained block move data out of ?ve bytes (and wss is not previously set), ?ve bytes are transferred out of memory to the scsi controller, four bytes are transferred from the scsi controller across the scsi bus, and one byte is temporarily stored in the lower byte of the sodl register waiting to be married with the ?rst byte of the next block move instruction. regardless of whether a chained block move or normal block move instruction is used, if the wss bit is set at the start of a data send command, the ?rst byte of the data send command is assumed to be the high-order byte and is married with the low-order byte stored in the lower byte of the sodl register before the two bytes are sent across the scsi bus. for n consecutive wide data send block move commands, the ?rst through the (n th - 1) block move instructions should be chained block moves.
2-54 functional description figure 2.9 block move and chained block move instructions chmov 5, 3 when data_out moves ?ve bytes from address 0x03 in the host memory to the scsi bus. bytes 0x03, 0x04, 0x05, and 0x06 are moved and byte 0x07 remains in the low-order byte of the scsi output data latch (sodl) register and is combined with the ?rst byte of the following move instruction. move 5, 9 when data_out moves ?ve bytes from address 0x09 in the host memory to the scsi bus. 0x03 0x02 0x01 0x00 0x07 0x06 0x05 0x04 0x0b 0x0a 0x09 0x08 0x0f 0x0e 0x0d 0x0c 0x13 0x12 0x11 0x10 0x04 0x03 0x06 0x05 0x09 0x07 0x0b 0x0a 0x0d 0x0c 32 bits 16 bits host memory scsi bus 00 04 08 0c 10
parallel rom interface 2-55 2.3 parallel rom interface the SYM53C896 supports up to one megabyte of external memory in binary increments from 16 kbytes to allow the use of expansion rom for add-in pci cards. both functions of the device share the rom interface. this interface is designed for low speed operations such as downloading instruction code from rom. it is not intended for dynamic activities such as executing instructions. system requirements include the SYM53C896, two or three external 8-bit address holding registers (hct273 or hct374), and the appropriate memory device. the 4.7 k w pull-up resistors on the mad bus require hc or hct external components to be used. if in-system flash rom updates are required, a 7406 (high voltage open collector inverter), a mtd4p05, and several passive components are also needed. the memory size and speed is determined by pull-up resistors on the 8-bit bidirectional memory bus at power-up. the SYM53C896 senses this bus shortly after the release of the reset signal and con?gures the expansion rom base address register and the memory cycle state machines for the appropriate conditions. the external memory interface works with a variety of rom sizes and speeds. an example set of interface drawings is in appendix b, external memory interface diagram examples . the SYM53C896 supports a variety of sizes and speeds of expansion rom, using pull-down resistors on the mad[3:0] pins. the encoding of pins mad[3:1] allows the user to de?ne how much external memory is available to the SYM53C896. table 2.7 shows the memory space
2-56 functional description associated with the possible values of mad[3:1]. the mad[3:1] pins are fully described in chapter 3, signal descriptions . to use one of the con?gurations mentioned above in a host adapter board design, put 4.7 k w pull-up resistors on the mad pins corresponding to the available memory space. for example, to connect to a 64 kbytes external rom, use a pull-up on mad[2]. if the external memory interface is not used, mad[3:1] should be pulled high. note: there are internal pull-downs on all of the mad bus signals. the SYM53C896 allows the system to determine the size of the available external memory using the expansion rom base address register in the pci con?guration space. for more information on how this works, refer to the pci speci?cation or the expansion rom base address register description in chapter 4, registers . mad[0] is the slow rom pin. when pulled up, it enables two extra clock cycles of data access time to allow use of slower memory devices. the external memory interface also supports updates to ?ash memory. table 2.7 parallel rom support mad[3:1] available memory space 000 16 kbytes 001 32 kbytes 010 64 kbytes 011 128 kbytes 100 256 kbytes 101 512 kbytes 110 1024 kbytes 111 no external memory present
serial eeprom interface 2-57 2.4 serial eeprom interface the SYM53C896 implements an interface that allows attachment of a serial eeprom device to the gpio0 and gpio1 pins for each scsi function. there are two modes of operation relating to the serial eeprom and the subsystem id and subsystem vendor id registers for each scsi function. these modes are programmable through the mad[7] pin which is sampled at power-up or hard reset. 2.4.1 default download mode in this mode, mad[7] is pulled down internally, gpio0 is the serial data signal (sda) and gpio1 is the serial clock signal (scl). certain data in the serial eeprom is automatically loaded into chip registers at power-up or hard reset. the format of the serial eeprom data is de?ned in table 2.8 . if the download is enabled and an eeprom is not present, or the checksum fails, the subsystem id and subsystem vendor id registers read back all zeros. at power-up or hard reset, only ?ve bytes are loaded into the chip from locations 0xfb through 0xff. the subsystem id and subsystem vendor id registers are read only, in accordance with the pci speci?cation, with a default value of all zeros if the download fails.
2-58 functional description 2.4.2 no download mode when mad[7] is pulled up through an external resistor, the automatic download is disabled and no data is automatically loaded into chip registers at power-up or hard reset. the subsystem id and subsystem vendor id registers are read only, per the pci speci?cation, with a default value of 0x1000 and 0x1000 respectively. 2.5 power management the SYM53C896 complies with the pci bus power management interface speci?cation, revision 1.1. the pci function power states d0, d1, d2, and d3 are de?ned in that speci?cation. d0 is the maximum powered state, and d3 is the minimum powered state. power state d3 is further categorized as d3hot or d3cold. a function that is powered off is said to be in the d3cold power state. table 2.8 mode a serial eeprom data format byte name description 0xfb svid(0) subsystem vendor id , lsb. this byte is loaded into the least signi?cant byte of the subsystem vendor id register in the appropriate pci con?guration space at chip power-up or hard reset. 0xfc svid(1) subsystem vendor id , msb. this byte is loaded into the most signi?cant byte of the subsystem vendor id register in the appropriate pci con?guration space at chip power-up or hard reset. 0xfd sid(0) subsystem id , lsb. this byte is loaded into the least signi?cant byte of the subsystem id register in the appropriate pci con?guration space at chip power-up or hard reset. 0xfe sid(1) subsystem id , msb. this byte is loaded into the most signi?cant byte of the subsystem id register in the appropriate pci con?guration space at chip power-up or hard reset. 0xff cksum checksum. this 8-bit checksum is formed by adding, bytewise, each byte contained in locations 0x00C0x03 to the seed value 0x55, and then taking the 2s complement of the result. 0x100Ceom ud user data.
power management 2-59 the SYM53C896 power states are independently controlled through two power state bits that are located in the pci con?guration space power management control/status (pmcsr) register 0x44C0x45 . although the pci bus power management interface speci?cation does not allow power state transitions d2 to d1, d3 to d2, or d3 to d1, the SYM53C896 hardware places no restriction on transitions between power states. the pci function power states d0, d1, d2, and d3 are described below in conjunction with each scsi function. power state actions are separate for each function. as the device transitions from one power level to a lower one, the attributes that occur from the higher power state level are carried over into the lower power state level. for example, d1 disables the scsi clk. therefore, d2 will include this attribute as well as the attributes de?ned in the power state d2 section. the pci function power states - d0, d1, d2, and d3 are described below in conjunction with each scsi function. power state actions are separate for each function. 2.5.1 power state d0 power state d0 is the maximum power state and is the power-up default state for each function. the SYM53C896 is fully functional in this state. 2.5.2 power state d1 power state d1 is a lower power state than d0. a function in this state places the SYM53C896 core in the snooze mode and disables the scsi table 2.9 power states con?guration register 0x44 bits [1:0] power state function 00 d0 maximum power 01 d1 disables scsi clock 10 d2 coma mode 11 d3 minimum power
2-60 functional description clk. in the snooze mode, a scsi reset does not generate an irq/ signal. 2.5.3 power state d2 power state d2 is a lower power state than d1. a function in this state places the SYM53C896 core in the coma mode. the following pci con?guration space command register enable bits are suppressed: i/o space enable memory space enable bus mastering enable serr/enable enable parity error response thus, the function's memory and i/o spaces cannot be accessed, and the function cannot be a pci bus master. furthermore, scsi and dma interrupts are disabled when the function is in power state d2. if the function is changed from power state d2 to power state d1 or d0, the previous values of the pci command register are restored. also, any pending interrupts before the function entered power state d2 are asserted. 2.5.4 power state d3 power state d3 is the minimum power state, which includes settings called d3hot and d3cold. d3hot allows the device to transition to d0 using software. the SYM53C896 is considered to be in power state d3cold when power is removed from the device. d3cold can transition to d0 by applying v cc and resetting the device. power state d3 is a lower power level than power state d2. a function in this state places the SYM53C896 core in the coma mode. furthermore, the function's soft reset is continually asserted while in power state d3, which clears all pending interrupts and 3-states the scsi bus. in addition, the function's pci command register is cleared. if both of the SYM53C896 functions are placed in power state d3, the clock quadrupler is disabled, which results in additional power savings.
symbios SYM53C896 pci to dual channel ultra2 scsi multifunction controller 3-1 chapter 3 signal descriptions this chapter presents the SYM53C896 pin con?guration and signal de?nitions using tables and illustrations. figure 3.1 is the functional signal grouping. the signal descriptions begin with table 3.2 . the signal descriptions are organized into functional groups: section 3.1, internal pull-ups on SYM53C896 signals section 3.2, pci bus interface signals section 3.3, scsi bus interface signals section 3.4, rom flash and memory interface signals section 3.5, test interface signals section 3.6, power and ground signals section 3.7, mad bus programming the pci interface signals are divided into the following functional groups: system signals , address and data signals , interface control signals , arbitration signals , error reporting signals , interrupt signals , scsi function a gpio signals , and scsi function b gpio signals . the scsi bus interface signals are divided into scsi function a signals , and scsi function b signals groups. a slash (/) at the end of a signal name indicates that the active state occurs when the signal is at a low voltage. when the slash is absent, the signal is active at a high voltage.
3-2 signal descriptions figure 3.1 SYM53C896 functional signal grouping clk rst/ ad[63:0] c_be[7:0] pa r par64 ack64/ req64/ frame/ trdy/ irdy/ stop/ devsel/ idsel req/ gnt/ perr/ serr/ inta/ intb/ alt_inta/ alt_intb/ int_dir a_gpio0_fetch/ a_gpio1_master/ a_gpio2 a_gpio3 a_gpio4 b_gpio0_fetch/ b_gpio1_master/ b_gpio2 b_gpio3 b_gpio4 mwe/ mce/ moe/_testout mas0/ mas1/ mad[7:0] sclk a_sd[15:0]/ a_sdp[1:0]/ a_sc_d/ a_si_o/ a_smsg/ a_sreq/ a_sack/ a_sack2/ a_sbsy/ a_satn/ a_srst/ a_ssel/ b_sdp[1:0]/ b_sc_d/ b_si_o/ b_smsg/ b_sreq/ b_sack/ b_sack2/ b_sbsy/ b_satn/ b_srst/ b_ssel/ b_sd[15:0]/ test_rst/ test_hsc moe/_testout tck tms tdi tdo b_diffsens a_diffsens SYM53C896 scsi function a scsi function b test interface scsi bus interface system address and data interface control arbitration error reporting interrupt scsi function a gpio scsi function b gpio rom flash and memory interface pci bus interface a_sctrl/ b_sctrl/ a_sreq2/ b_sreq2/
3-3 there are ?ve signal type de?nitions: i input, a standard input-only signal. o output, a standard output driver (typically a totem pole output). i/o input and output (bidirectional). t/s 3-state, a bidirectional, 3-state input/output signal. s/t/s sustained 3-state, an active low 3-state signal owned and driven by one and only one agent at a time.
3-4 signal descriptions 3.1 internal pull-ups on SYM53C896 signals several SYM53C896 signals use internal pull-ups and pull-downs. the following table describes the conditions that enable these pull-ups and pull-downs. table 3.1 SYM53C896 internal pull-ups and pull-downs pin name pull-up current conditions for pull-up inta/, intb/, alt_inta/, alt_intb/ 25 m a pull-up enabled when the and-tree mode is enabled by driving test_rst/ low or when the irq mode bit (bit 3 of dcntl, 0x3b) is cleared. 1 int_dir, tck, tdi, test_rst/, tms 25 m a pulled up internally. ad[63:32], c_be[7:4], par64 25 m a pulled up internally if not used. gpio[4:0] - 25 m a pulled down internally when con?gured as inputs. mad[7:0] - 25 m a pulled down internally. tdo, test_hsc - 25 m a pulled down internally. 1. when bit 3 of dma control (dcntl) is set, the pad becomes a totem pole output pad and will drive both high and low.
pci bus interface signals 3-5 3.2 pci bus interface signals the pci bus interface signals section contains tables describing the signals for the following signal groups: system signals , address and data signals , interface control signals , arbitration signals , error reporting signals , interrupt signals , scsi function a gpio signals , and scsi function b gpio signals . 3.2.1 system signals this section describes the signals for the system signals group. table 3.2 system signals name bump type strength description clk h3 i n/a clock provides timing for all transactions on the pci bus and is an input to every pci device. all other pci signals are sampled on the rising edge of clk, and other timing parameters are de?ned with respect to this edge. clock can optionally serve as the scsi core clock, but this may effect fast scsi-2 (or faster) transfer rates. rst/ g1 i n/a reset forces the pci sequencer of each device to a known state. all t/s and s/t/s signals are forced to a high impedance state, and all internal logic is reset. the rst/ input is synchronized internally to the rising edge of clk. the clk input must be active while rst/ is active to properly reset the device.
3-6 signal descriptions 3.2.2 address and data signals this section describes the signals for the address and data signals group. table 3.3 address and data signals name bump type strength description ad[63:0] y5, ab5, ac5, aa6, y6, ab6, ac6, aa7, ab7, ac7, aa8, y8, ab8, ac8, aa9, y9, ab9, ac9, aa10, y11, ab10, ac10, aa11, ac11, ab11, ac12, aa12, ab12, ab13, ac13, aa13, ac14, h1, j3, j4, j2, j1, k3, l4, k2, l1, l2, m1, m3, m2, n2, n1, n3, t4, t3, u1-u3, v1, v2, v4, w1, w2, w4, w3, y1, y2, aa1, y3. t/s 16 ma pci physical dword address and data are multiplexed on the same pci pins. a bus transaction consists of an address phase followed by one or more data phases. during the ?rst clock of a transaction, ad[63:0] contain a 64-bit physical byte address. if the command is a dac, implying a 64-bit address, ad[31:0] will contain the upper 32 bits of the address during the second clock of the transaction. during subsequent clocks, ad[63:0] contain data. pci supports both read and write bursts. ad[7:0] de?ne the least signi?cant byte, and ad[63:56] de?ne the most signi?cant byte. c_be[7:0]/ aa4, ac3, ab4, ac4, k1, p1, t2, v3. t/s 16 ma pci bus command and byte enables are multiplexed on the same pci pins. during the address phase of a transaction, c_be[3:0]/ de?ne the bus command. if the transaction is a dac, c_be[3:0]/ contain the dac command and c_be[7:4]/ de?ne the bus command. c_be[3:0]/ de?ne the bus command during the second clock of the transaction. during the data phase, c_be[7:0]/ are used as byte enables. the byte enables determine which byte lanes carry meaningful data. c_be[0]/ applies to byte 0, and c_be[7]/ to byte 7. par t1 t/s 16 ma pci parity is the even parity bit that protects the ad[31:0] and c_be[3:0]/ lines. during the address phase, both the address and command bits are covered. during data phase, both data and byte enables are covered.
pci bus interface signals 3-7 3.2.3 interface control signals this section describes the signals for the interface control signals group. par64 aa5 t/s 16 ma pci parity64 is the even parity bit that protects the ad[63:32] and c_be[7:4]/ lines. during address phase, both the address and command bits are covered. during data phase, both data and byte enables are covered. table 3.3 address and data signals (cont.) name bump type strength description table 3.4 interface control signals name bump type strength description ack64/ ab1 s/t/s 16 ma pci acknowledge 64 -bit transfer is driven by the current bus target to indicate its ability to transfer 64-bit data. req64/ aa2 s/t/s 16 ma pci request 64 -bit transfer is driven by the current bus master to indicate a request to transfer 64-bit data. frame/ p2 s/t/s 16 ma pci cycle frame is driven by the current master to indicate the beginning and duration of an access. frame/ is asserted to indicate that a bus transaction is beginning. while frame/ is deasserted, either the transaction is in the ?nal data phase or the bus is idle. trdy/ p3 s/t/s 16 ma pci target ready indicates the target agents (selected devices) ability to complete the current data phase of the transaction. trdy/ is used with irdy/. a data phase is completed on any clock when used with irdy/. a data phase is completed on any clock when both trdy/ and irdy/ are sampled asserted. during a read, trdy/ indicates that valid data is present on ad[31:0]. during a write, it indicates that the target is prepared to accept data. wait cycles are inserted until both irdy/ and trdy/ are asserted together. irdy/ n4 s/t/s 16 ma pci initiator ready indicates the initiating agents (bus masters) ability to complete the current data phase of the transaction. irdy/ is used with trdy/. a data phase is completed on any clock when both irdy/ and trdy/ are sampled asserted. during a write, irdy/ indicates that valid data is present on ad[31:0]. during a read, it indicates that the master is prepared to accept data. wait cycles are inserted until both irdy/ and trdy/ are asserted together.
3-8 signal descriptions 3.2.4 arbitration signals this section describes the signals for the arbitration signals group. stop/ r2 s/t/s 16 ma pci stop indicates that the selected target is requesting the master to stop the current transaction. devsel/ r1 s/t/s 16 ma pci device select indicates that the driving device has decoded its address as the target of the current access. as an input, it indicates to a master whether any device on the bus has been selected. idsel l3 i n/a initialization device select is used as a chip select in place of the upper 24 address lines during con?guration read and write transactions. table 3.4 interface control signals (cont.) name bump type strength description table 3.5 arbitration signals name bump type strength description req/ h2 o 16 ma pci request indicates to the system arbiter that this agent desires use of the pci bus. this is a point-to-point signal. both scsi functions share the req/ signal. gnt/ h4 i n/a grant indicates to the agent that access to the pci bus has been granted. this is a point-to-point signal. both scsi functions share the gnt/ signal.
pci bus interface signals 3-9 3.2.5 error reporting signals this section describes the signals for the error reporting signals group. table 3.6 error reporting signals name bump type strength description perr/ r4 s/t/s 16 ma pci parity error may be pulsed active by an agent that detects a data parity error. perr/ can be used by any agent to signal data corruption. however, on detection of a perr/ pulse, the central resource may generate a nonmaskable interrupt to the host cpu, which often implies the system is unable to continue operation once error processing is complete. serr/ r3 o 16 ma pci system error is an open drain output used to report address parity errors as well as critical errors other than parity.
3-10 signal descriptions 3.2.6 interrupt signals this section describes the interrupt signals group. table 3.7 interrupt signals name 1 bump type strength description inta/ f4 o 16 ma pci interrupt function a. this signal, when asserted low, indicates an interrupting condition in scsi function a and that service is required from the host cpu. the output drive of this pin is open drain. if the scsi function b interrupt is rerouted at power-up using the inta/ enable sense resistor (pull-up on mad[4]), this signal indicates that an interrupting condition has occurred in either the scsi function a or scsi function b. this interrupt pin is disabled if int_dir is driven low. intb/ f2 o 16 ma pci interrupt function b. this signal, when asserted low, indicates an interrupting condition has occurred in the scsi function b and that service is required from the host cpu. the output drive of this pin is open drain. this interrupt can be rerouted to inta/ at power-up using the inta/ enable sense resistor (pull-up on mad[4]). this causes the SYM53C896 to program the scsi function b pci interrupt pin register ( 0x3d ) to 0x01. this interrupt pin is disabled if int_dir is driven low. alt_inta/ f1 o 16 ma pci alt interrupt function a. when asserted low, it indicates an interrupting condition has occurred in scsi function a. the output drive of this pin is open drain. if the scsi function b interrupt was rerouted at power-up using the inta/ enable sense resistor (pull-up on mad[4]), this signal indicates that an interrupting condition has occurred in either the scsi function a or scsi function b. alt_intb/ g3 o 16 ma pci alt interrupt function b. when asserted low, indicates an interrupting condition has occurred in scsi function b. the output drive of this pin is open drain. this interrupt can be rerouted to inta/ at power-up using the inta/ enable sense resistor (pull-up on mad[4]). this will cause the SYM53C896 to program the function b pci interrupt pin register ( 0x3d ) to 0x01. int_dir g2 i n/a interrupt direction. this input signal indicates whether internally generated interrupts will be presented on inta/ and intb/. if int_dir is high, internal interrupts will be generated on both the intx/ pins and the alt_intx pin. if int_dir is low, the internal interrupts will be generated only on the alt_intx/ pin. this pin has a static pull-up. 1. see register 0x4d, scsi test one (stest1) in chapter 4, registers for additional information on these signals.
pci bus interface signals 3-11 3.2.7 scsi function a gpio signals this section describes the signals for the scsi function a gpio group. table 3.8 scsi function a gpio signals name bump type strength description a_gpio0_ fetch/ ab16 i/o 8 ma scsi function a general purpose i/o pin 0. this pin is programmable at power-up through the mad[7] pin to serve as the data signal for the serial eeprom interface. when gpio_0 is not in the process of downloading eeprom data it can be used to drive a scsi activity led if bit 5 in the general purpose pin control (gpcntl) register is set. or, it can be used to indicate that the next bus request will be an opcode fetch if bit 6 in the gpcntl register is set. a_gpio1_ master/ y16 i/o 8 ma scsi function a general purpose i/o pin 1. this pin is programmable at power-up through the mad[7] pin to serve as the clock signal for the serial eeprom interface. when general purpose pin control (gpcntl) bit 7 is set, this pin drives low when the SYM53C896 is bus master. a_gpio2 aa16 i/o 8 ma scsi function a general purpose i/o pin 2. this pin powers up as an input. a_gpio3 ac17 i/o 8 ma scsi function a general purpose i/o pin 3. this pin powers up as an input. a_gpio4 ab17 i/o 8 ma scsi function a general purpose i/o pin 4. this pin powers up as an output.
3-12 signal descriptions 3.2.8 scsi function b gpio signals this section describes the signals for the scsi function b gpio group. table 3.9 scsi function b gpio signals name bump type strength description b_gpio0_ fetch/ aa14 i/o 8 ma scsi function b general purpose i/o pin 0. this pin is programmable at power-up through the mad[7] pin to serve as the data signal for the serial eeprom interface. when gpio_0 is not in the process of downloading eeprom data it can be used to drive a scsi activity led if bit 5 in the general purpose pin control (gpcntl) register is set. or, it can be used to indicate that the next bus request will be an opcode fetch if bit 6 in the gpcntl register is set. b_gpio1_ master/ ac15 i/o 8 ma scsi function b general purpose i/o pin 1. this pin is programmable at power-up through the mad[7] pin to serve as the clock signal for the serial eeprom interface. when general purpose pin control (gpcntl) bit 7 is set, this pin is driven low when the SYM53C896 is bus master. b_gpio2 ab15 i/o 8 ma scsi function b general purpose i/o pin 2. this pin powers up as an input. b_gpio3 aa15 i/o 8 ma scsi function b general purpose i/o pin 3. this pin powers up as an input. b_gpio4 ac16 i/o 8 ma scsi function b general purpose i/o pin 4. this pin powers up as an output.
scsi bus interface signals 3-13 3.3 scsi bus interface signals the scsi bus interface signals section contains tables describing the signals for the following signal groups: scsi bus interface signals , scsi function a signals , and scsi function b signals . scsi function a signals and scsi function b signals each have a subgroup: scsi function a_sctrl signals signals and scsi function b_scrtl signals signals. the following table contains signals that are common to both scsi buses. 3.3.1 scsi function a signals this section describes the signals for the scsi function a signals group. it is divided into two tables: scsi function a signals and scsi function a_sctrl signals . table 3.10 scsi bus interface signals name bump type strength description sclk a21 i n/a scsi clock is used to derive all scsi-related timings. the speed of this clock is determined by the applications requirements. in some applications, sclk may be sourced internally from the pci bus clock (clk). if sclk is internally sourced, then the sclk pin should be tied low. for ultra2 scsi operations, the clock supplied to sclk must be 40 mhz. the clock frequency will be quadrupled to create the 160 mhz clock required internally by both scsi functions.
3-14 signal descriptions table 3.11 scsi function a signals name bump type strength description a_sd[15:0] - a_sdp[1:0] - b5, c5, b4, c4, d19, a19, d18, a18, d11, a9, d9, a8, d8, a7, c7, b6. c6, a10. i/o 48 ma scsi scsi function a data and parity. lvd mode: negative half of lvd link pair for scsi data and parity lines. a_sd[15:0] - are the 16-bit scsi data bus, and a_sdp[1:0] - are the scsi data parity lines. se mode: a_sd[15:0] - are the 16-bit scsi data bus, and a_sdp[1:0] - are the scsi data parity lines. hvd mode: a_sd[15:0] - and a_sdp[1:0] - are the scsi data bus. a_sd[15:0]+ a_sdp[1:0]+ a5, d5, a4, a3, c19, b19, c18, b18, b10, c10, b9, c9, b8, c8, b7, a6. d6, c11. i/o 48 ma scsi scsi function a data and parity. lvd mode: positive half of lvd link pair for scsi data lines. a_sd[15:0]+ are the 16-bit data bus, and a_sdp[1:0]+ are the scsi data parity lines. se mode: a_sd[15:0]+ and a_sdp[1:0]+ are at 0 v. hvd mode: a_sd[15:0]+ and a_sdp+ are driver directional control for scsi data lines. a_diffsens a20 i n/a scsi function a differential sense pin detects the present mode of the scsi bus when connected to the diffsens signal on the physical scsi bus. lvd mode: when a voltage between 0.7 v and 1.9 v is present on this pin, the scsi function a will operate in the lvd mode. se mode: when this pin is driven low (below 0.5 v) indicating se bus operation, the scsi function a will operate in the se mode. hvd mode: when this pin is detected high (above 2.4 v) indicating a hvd bus, the scsi function a will 3-state its scsi drivers. set the dif bit in scsi test two (stest2) to enable hvd drivers.
scsi bus interface signals 3-15 3.3.1.1 a_sctrl signals table 3.12 scsi function a_sctrl signals name bump type strength description scsi function a control includes the following signals: a_sc_d - a_sc_d+ a_si_o - a_si_o+ a_smsg - a_smsg+ a_sreq - a_sreq+ a_sreq2 - a_sreq2+ a_sack - a_sack+ a_sack2 - a_sack2+ a_sbsy - a_sbsy+ a_satn - a_satn+ a_srst - a_srst+ a_ssel - a_ssel+ c15 a16 b17 c17 c14 a15 c16 a17 b16 d16 c13 a14 b13 a13 c12 a12 b11 b12 b14 d13 b15 d15 i/o 48 ma scsi scsi phase line, command/data. scsi phase line, input/output. scsi phase line, message. data handshake line from target device. data handshake line from target device. duplicate of a_sreq - enabled by pulling mad[5] high at reset. data handshake signal from the initiator device. data handshake signal from the initiator device. duplicate of b_sack - and b_sack+ enabled by pulling mad[5] high at reset. scsi bus arbitration signal, busy. scsi attention, the initiator is requesting a message out phase. scsi bus reset. scsi bus arbitration signal, select device. for all a_sctrl signals: lvd mode: negative and positive halves of lvd link signal pairs shown for scsi function a control. se mode: scsi function a control signals shown. + signals are at 0 v. hvd mode: scsi function a control signals shown. + signals become direction control.
3-16 signal descriptions 3.3.2 scsi function b signals this section describes the signals for the scsi function b signals group. it is divided into two tables: scsi function b signals and scsi function b_scrtl signals . table 3.13 scsi function b signals name bump type strength description b_sd[15:0] - b_sdp[1:0] - f21, e22, e21, d22, y22, w21, w22, v21, k23, l20, j23, j20, h23, h20, g23, g21. f22, l23. i/o 48 ma scsi scsi function b data and parity. lvd mode: negative half of lvd link pair for scsi data and parity lines. b_sd[15:0] - are the 16-bit scsi data bus, and b_sdp[1:0] - are the scsi data parity lines. se mode: b_sd[15:0] - are the 16-bit scsi data bus, and b_sdp[1:0] - are the scsi data parity lines. hvd mode: b_sd[15:0] - and b_sdp[1:0] - are the scsi data bus. b_sd[15:0]+ b_sdp[1:0]+ f20, e23, e20, d23, aa23, y23, w20, w23, l21, k22, k21, j22, j21, h22, h21, g22. f23, l22. i/o 48 ma scsi scsi function b data and parity. lvd mode: positive half of lvd link pair for scsi data lines. b_sd[15:0]+ are the 16-bit data bus, and b_sdp[1:0]+ are the scsi data parity lines. se mode: b_sd[15:0]+ and b_sdp[1:0]+ are at 0 v. hvd mode: b_sd[15:0]+ and b_sdp[1:0]+ are driver directional control for scsi data lines.
scsi bus interface signals 3-17 b_diffsens y21 i n/a scsi function b differential sense pin detects the present mode of the scsi bus when connected to the diffsens signal on the physical scsi bus. lvd mode: when a voltage between 0.7 v and 1.9 v is present on this pin, the scsi function b will operate in the lvd mode. se mode: when this pin is driven low (below 0.5 v) indicating se bus operation, the scsi function b will operate in the se mode. hvd mode: when this pin is detected high (above 2.4 v) indicating a hvd bus, the scsi function b will 3-state its scsi drivers. set the dif bit in stest2 to enable hvd drivers. table 3.13 scsi function b signals (cont.) name bump type strength description
3-18 signal descriptions table 3.14 scsi function b_scrtl signals name bump type strength description scsi function b control includes the following signals: b_sc_d - b_sd_d+ b_si_o - b_si_o+ b_smsg - b_smsg+ b_sreq - b_sreq+ b_sreq2 - b_sreq2+ b_sack - b_sack+ b_sack2 - b_sack2+ b_sbsy - b_sbsy+ b_satn - b_satn+ b_srst - b_srst+ b_ssel - b_ssel+ t20 t21 v22 v20 r20 r21 u21 v23 u23 u22 n20 p21 p23 p22 n23 n21 m23 n22 r23 r22 t23 t22 i/o 48 ma scsi scsi phase line, command/data. scsi phase line, input/output. scsi phase line, message. data handshake line from target device. data handshake line from target device. duplicate of b_sreq - enabled by pulling mad[6] high at reset. data handshake signal from the initiator device. data handshake signal from the initiator device. duplicate of b_sack - and b_sack+ enabled by pulling mad[6] high at reset. scsi bus arbitration signal, busy. scsi attention, the initiator is requesting a message out phase. scsi bus reset. scsi bus arbitration signal, select device. for all b_scrtl signals: lvd mode: negative and positive halves of lvd link signal pairs shown for scsi function b control. se mode: scsi function b control signals shown. + signals are at 0 v. hvd mode: scsi function b control signals shown. + signals become direction control.
rom flash and memory interface signals 3-19 3.4 rom flash and memory interface signals this section describes the signals for the rom flash and memory interface signals group. table 3.15 rom flash and memory interface signals name bump type strength description mwe/ ac19 o 4 ma memory write enable. this pin is used as a write enable signal to an external ?ash memory. mce/ aa18 o 4 ma memory chip enable. this pin is used as a chip enable signal to an external eprom or ?ash memory device. moe/_ testout y18 o 4 ma memory output enable. this pin is used as an output enable signal to an external eprom or ?ash memory during read operations. it is also used to test the connectivity of the SYM53C896 signals in the and- tree test mode. the moe/_testout pin is only driven as the test out function when the zmode bit ( chip control 1 (ccntl1) , bit 7) is set. mas0/ ac18 o 4 ma memory address strobe 0 . this pin is used to latch in the least signi?cant address byte (bits [7:0]) of an external eprom or ?ash memory. since the SYM53C896 moves addresses eight bits at a time, this pin connects to the clock of an external bank of ?ip-?ops which are used to assemble up to a 20-bit address for the external memory. mas1/ aa17 o 4 ma memory address strobe 1. this pin is used to latch in the most signi?cant address byte (bits [15:8]) of an external eprom or ?ash memory. since the SYM53C896 moves addresses eight bits at a time, this pin connects to the clock of an external bank of ?ip-?ops which assemble up to a 20-bit address for the external memory. mad[7:0] y19, aa19, ac20, ab20, aa20, ac22, ab21, ac23. i/o 4 ma memory address/data bus. this bus is used in conjunction with the memory address strobe pins and external address latches to assemble up to a 20-bit address for an external eprom or ?ash memory. this bus will put out the least signi?cant byte ?rst and ?nish with the most signi?cant bits. it is also used to write data to a ?ash memory or read data into the chip from external eprom/?ash memory. these pins have static pull-downs.
3-20 signal descriptions 3.5 test interface signals this section describes the signals for the test interface group. the table is divided into internal test signals and jtag signals . table 3.16 test interface signals name bump type strength description internal test signals test_hsc c23 i n/a test halt scsi clock. for lsi logic test purposes only. pulled low internally. this signal can also cause a full chip reset. test_rst/ c1 i n/a test reset. for lsi logic test purposes only. pulled high internally. moe/_ testout y18 o 4 ma memory output enable. this pin is used as an output enable signal to an external eprom or ?ash memory during read operations. it is also used to test the connectivity of the SYM53C896 signals in the and-tree test mode. the moe/_testout pin is only driven as the test out function when the zmode bit ( chip control 1 (ccntl1) , bit 7) is set. jtag signals tck d1 i n/a test clock. this pin provides the clock for the jtag test logic. tms e3 i n/a test mode select . the signal received at tms is decoded by the tap controller to control jtag test operations. tdi e2 i n/a test data in. serial test instructions are received by the jtag test logic at this pin. tdo e1 o 4 ma test data out. this pin is the serial output for test instructions and data from the jtag test logic. reserved ab14 reserved. not used.
power and ground signals 3-21 3.6 power and ground signals this section describes the signals for the power and ground signals group. table 3.17 power and ground signals name 1 bump type strength description v ss d4, d12, d20, m4, m10C14, m20, aa3, aa21, k10C14, l10C14, c3, c21, n10C14, p10C14, y4, y12, y20. g n/a ground for pci bus drivers/receivers, scsi bus drivers/receivers, local memory interface drivers, and other i/o pins. v dd d7, d10, d14, d17, g4, g20, k4, k20, p4, p20, u4, u20, y7, y10, y14, y17. p n/a power for pci bus drivers/receivers, scsi bus drivers/receivers, local memory interface drivers/receivers, and other i/o pins. v dd -core d3, e4, y13, ab18. p n/a power for core logic. v ss -core d2, f3, y15, ab19, ac21. g n/a ground for core logic. v dd -a c20 p n/a power for analog cells (clock quadrupler and diffsense logic). v ss -a b20 g n/a ground for analog cells (clock quadrupler and diffsense logic). v dd -bias m22 p n/a power for lvd bias current. v dd -bias2 a11 p n/a power for lvd bias current.
3-22 signal descriptions rbias m21 i n/a used to connect an external resistor to generate the bias current used by lvd link pads. resistor value should be 9.76 k w . connect other end of resistor to v dd . nc a1, a2, a22, a23, b1C3, b21C23, c2, c22, d21, ab2, ab3, ac1, ac2, aa22, ab22, ab23. n/a n/a these pins have no internal connection. 1. the i/o driver pad rows and digital core have isolated power supplies as indicated by the i/o and core extensions on their respective v ss and v dd names. these power and ground pins should be connected directly to the primary power and ground planes of the circuit board. bypass capacitors of 0.01 m f should be applied between adjacent v ss and v dd pairs wherever possible. do not connect bypass capacitors between v ss and v dd pairs that cross power and ground bus boundaries. table 3.17 power and ground signals (cont.) name 1 bump type strength description
mad bus programming 3-23 3.7 mad bus programming the mad[7:0] pins, in addition to serving as the address/data bus for the local memory interface, also are used to program power-up options for the chip. a particular option is programmed allowing the internal pull-down current sink to pull the pin low at reset or by connecting a 4.7 k w resistor between the appropriate mad[x] pin and v ss . the pull-down resistors require that hc or hct external components are used for the memory interface. mad[7] serial eeprom programmable option. when allowed to be pulled low by the internal pull-down current sink, the automatic data download is enabled. when pulled high by an external resistor, the automatic data download is disabled. please see section 2.4, serial eeprom interface and subsystem id and subsystem vendor id registers in chapter 4, registers for additional information. mad[6] enable b duplicate scsi req/ and ack/ signals. when allowed to be pulled low by the internal pull-down current sink, the duplicate scsi req/ and ack/ signals for channel b are disabled. when pulled high by an external resistor, the duplicate scsi req/ and ack/ signals for channel b are enabled. mad[5] enable a duplicate scsi req/ and ack/ signals. when allowed to be pulled low by the internal pull-down current sink, the duplicate scsi req/ and ack/ signals for channel a are disabled. when pulled high by an external resistor, the duplicate scsi req/ and ack/ signals for channel a are enabled. mad[4] inta/ routing enable. placing a pull-up resistor on this pin causes scsi function b interrupt requests to appear on the inta/ pin, along with scsi function a interrupt requests, instead of on intb/. placing a pull-up resistor on this pin also causes the scsi function b interrupt pin register ( 0x3d ) in pci con?guration space to be programmed to 0x01 instead of 0x02. placing no resistor on this pin causes scsi function b interrupt requests to appear on the intb/ pin. placing no resistor on this pin also causes the scsi function b interrupt pin register ( 0x3d ) in pci con?guration space to be programmed to 0x02. the mad[3:1] pins are used to set the size of the external expansion rom device attached. encoding for these pins is listed in table 3.18
3-24 signal descriptions (0 indicates a pull-down resistor is attached, 1 indicates a pull-up resistor attached). the mad[0] pin is the slow rom pin. when pulled up, it enables two extra cycles of data access time to allow use of slower memory devices. all mad pins have internal pull-down resistors. table 3.18 decode of mad[3:1] pins mad[3:1] available memory space 000 16 kbytes 001 32 kbytes 010 64 kbytes 011 128 kbytes 100 256 kbytes 101 512 kbytes 110 1024 kbytes 111 no external memory present
symbios SYM53C896 pci to dual channel ultra2 scsi multifunction controller 4-1 chapter 4 registers this section contains descriptions of all SYM53C896 registers. the term set is used to refer to bits that are programmed to a binary one. similarly, the term cleared is used to refer to bits that are programmed to a binary zero. write any bits marked as reserved to zero; mask all information read from them. reserved bit functions may change at any time. unless otherwise indicated, all bits in the registers are active high, that is, the feature is enabled by setting the bit. the bottom row of every register diagram shows the default register values, which are enabled after the chip is powered on or reset. this chapter contains the following sections: section 4.1, pci configuration registers section 4.2, scsi registers section 4.3, 64-bit scripts selectors section 4.4, phase mismatch jump registers 4.1 pci con?guration registers the pci con?guration registers are accessed by performing a con?guration read/write to the device with its idsel pin asserted and the appropriate value in ad[10:8] during the address phase of the transaction. scsi function a is identi?ed by a binary value of 0b000, and scsi function b by a value of 0b001. each scsi function contains the same register set with identical default values, except the interrupt pin register. table 4.1 shows the pci con?guration registers implemented in the SYM53C896.
4-2 registers all pci-compliant devices, such as the SYM53C896, must support the vendor id , device id , command , and status registers. support of other pci-compliant registers is optional. in the SYM53C896, registers that are not supported are not writable and return all zeros when read. only those registers and bits that are currently supported by the SYM53C896 are described in this chapter. note: reserved bits should not be accessed. registers: 0x00C0x01 vendor id read only vid vendor id [15:0] this 16-bit register identi?es the manufacturer of the device. the vendor id is 0x1000. table 4.1 pci con?guration register map 31 16 15 0 device id vendor id 0x00 status command 0x04 class code revision id (rev id) 0x08 not supported header type latency timer cache line size 0x0c base address register zero (i/o) 0x10 base address register one (memory) bits [31:0] 0x14 base address register one (memory) bits [63:32] 0x18 base address register two (scripts ram) bits [31:0] 0x1c base address register two (scripts ram) ) bits [63:32] 0x20 not supported 0x24 reserved 0x28 subsystem id subsystem vendor id 0x2c expansion rom base address 0x30 reserved capabilities pointer 0x34 reserved 0x38 max_lat min_gnt interrupt pin interrupt line 0x3c power management capabilities (pmc) next item pointer capability id 0x40 data bridge support exten- sions (pmcsr_bse) power management control/status (pmcsr) 0x44 15 0 vid 0001000000000000
pci con?guration registers 4-3 registers: 0x02C0x03 device id read only did device id [15:0] this 16-bit register identi?es the particular device. the SYM53C896 device id is 0x000b. registers: 0x04C0x05 command read/write the command register provides coarse control over a devices ability to generate and respond to pci cycles. when a zero is written to this register, the SYM53C896 is logically disconnected from the pci bus for all accesses except con?guration accesses. r reserved [15:9] se serr/ enable 8 this bit enables the serr/ driver. serr/ is disabled when this bit is cleared. the default value of this bit is zero. this bit and bit 6 must be set to report address parity errors. r reserved 7 eper enable parity error response 6 this bit allows the SYM53C896 to detect parity errors on the pci bus and report these errors to the system. only data parity checking is enabled and disabled with this bit. the SYM53C896 always generates parity for the pci bus. 15 0 did 0000000000000011 15 987 6 543 2 1 0 rse r eper r wie r ebm ems eis x x x x x x x0 x0 x0 x0 00
4-4 registers r reserved 5 wie write and invalidate enable 4 this bit allows the SYM53C896 to generate write and invalidate commands on the pci bus. the wie bit in the dma control (dcntl) register must also be set for the device to generate write and invalidate commands. r reserved 3 ebm enable bus mastering 2 this bit controls the ability of the SYM53C896 to act as a master on the pci bus. a value of zero disables this device from generating pci bus master accesses. a value of one allows the SYM53C896 to behave as a bus master. the device must be a bus master in order to fetch scripts instructions and transfer data. ems enable memory space 1 this bit controls the ability of the SYM53C896 to respond to memory space accesses. a value of zero disables the device response. a value of one allows the SYM53C896 to respond to memory space accesses at the address range speci?ed by the base address register one (mem- ory) and base address register two (scripts ram) registers in the pci con?guration space. eis enable i/o space 0 this bit controls the SYM53C896 response to i/o space accesses. a value of zero disables the device response. a value of one allows the SYM53C896 to respond to i/o space accesses at the address range speci?ed by the base address register zero (i/o) register in the pci con?guration space.
pci con?guration registers 4-5 registers: 0x06C0x07 status read/write reads to this register behave normally. writes are slightly different in that bits can be cleared, but not set. a bit is cleared whenever the register is written, and the data in the corresponding bit location is a one. for instance, to clear bit 15 and not affect any other bits, write the value 0x8000 to the register. dpe detected parity error (from slave) 15 this bit is set by the SYM53C896 whenever it detects a data parity error, even if data parity error handling is disabled. sse signaled system error 14 this bit is set whenever the device asserts the serr/ signal. rma received master abort (from master) 13 a master device should set this bit whenever its transaction (except for special cycle) is terminated with master abort. rta received target abort (from master) 12 a master device should set this bit whenever its transaction is terminated by target abort. r reserved 11 dt[1:0] devsel/ timing [10:9] these bits encode the timing of devsel/. these are encoded as: 15 14 13 12 11 10 9 8 7 5 4 3 0 dpe sse rma rta r dt[1:0] dpr rnc r 0000 x000 x x x1 x x x x 0b00 fast 0b01 medium 0b10 slow 0b11 reserved
4-6 registers these bits are read only and should indicate the slowest time that a device asserts devsel/ for any bus command except con?guration read and con?guration write. the SYM53C896 supports a value of 0b01. dpr data parity error reported 8 this bit is set when the following conditions are met: the bus agent asserted perr/ itself or observed perr/ asserted and; the agent setting this bit acted as the bus master for the operation in which the error occurred and; the parity error response bit in the command register is set. r reserved [7:5] nc new capabilities 4 this bit is set to indicate a list of extended capabilities such as pci power management. this bit is read only. r reserved [3:0] register: 0x08 revision id (rev id) read only rid revision id [7:0] this register speci?es a device speci?c revision identi?er. the upper nibble is always set to 0x0000. the lower nibble re?ects the current revision level of the device. 7 0 rid 0000xxxx
pci con?guration registers 4-7 registers: 0x09C0x0b class code read only cc class code [23:0] this 24-bit register is used to identify the generic function of the device. the upper byte of this register is a base class code, the middle byte is a subclass code, and the lower byte identi?es a speci?c register-level programming interface. the value of this register is 0x010000, which identi?es a scsi controller. register: 0x0c cache line size read/write cls cache line size [7:0] this register speci?es the system cache line size in units of 32-bit words. the value in this register is used by the device to determine whether to use write and invalidate or write commands for performing write cycles, and whether to use read, read line, or read multiple commands for performing read cycles as a bus master. devices participating in the caching protocol use this ?eld to know when to retry burst accesses at cache line boundaries. these devices can ignore the pci cache support lines (sdone and sb0/) when this register is set to 0. if this register is programmed to a number which is not a power of 2, the device will not use pci performance commands to perform data transfers. 23 0 cc 000000010000000000000000 7 0 cls 00000000
4-8 registers register: 0x0d latency timer read/write lt latency timer [7:0] the latency timer register speci?es, in units of pci bus clocks, the value of the latency timer for this pci bus master. the scsi functions of the SYM53C896 support this timer. all eight bits are writable, allowing latency values of 0C255 pci clocks. use the following equation to calculate an optimum latency value for the scsi functions of the SYM53C896. latency = 2 + (burst size x (typical wait states + 1)) values greater than optimum are also acceptable. register: 0x0e header type read only ht header type [7:0] this 8-bit register identi?es the layout of bytes 0x10 through 0x3f in con?guration space and also whether or not the device contains multiple functions. since the SYM53C896 is a multifunction controller the value of this register is 0x80. register: 0x0f not supported 7 0 lt 00000000 7 0 ht 00000000
pci con?guration registers 4-9 registers: 0x10C0x13 base address register zero (i/o) read/write bar0 base address register zero - i/o [31:0] this base address register is used to map the operating register set into i/o space. the SYM53C896 requires 256 bytes of i/o space for this base address register. it has bit zero hardwired to one. bit 1 is reserved and returns a zero on all reads, and the other bits are used to map the device into i/o space. for detailed information on the operation of this register, refer to the pci 2.1 speci?cation. registers: 0x14C0x1b base address register one (memory) read/write bar1 base address register one [63:0] this base address register maps scsi operating registers into memory space. this device requires 1024 bytes of address space for this base register. this register has bits [9:0] hardwired to 0b0000000100. the default value of this register is 0x0000000000000004. for detailed information on the operation of this register, refer to the pci 2.1 speci?cation. 31 0 bar0 00000000000000000000000000000001 63 32 bar1 00000000000000000000000000000000 31 0 bar1 00000000000000000000000000000100
4-10 registers registers: 0x1cC0x23 base address register two (scripts ram) read/write bar2 base address register two [63:0] this base register is used to map the scripts ram into memory space. the default value of this register is 0x0000000000000004. the SYM53C896 requires 8192 bytes of address space for this base register. this register has bits [12:0] hardwired to 0b0000000000100. for detailed information on the operation of this register, refer to the pci 2.1 speci?cation. registers: 0x24C0x27 not supported registers: 0x28C0x2b reserved 63 32 bar2 00000000000000000000000000000000 31 0 bar2 00000000000000000000000000000100
pci con?guration registers 4-11 registers: 0x2cC0x2d subsystem vendor id read only svid subsystem vendor id [15:0] this 16-bit register is used to uniquely identify the vendor manufacturing the add-in board or subsystem where this pci device resides. it provides a mechanism for an add-in card vendor to distinguish its cards from another vendors cards, even if the cards have the same pci controller installed on them (and therefore the same vendor id and device id). if the external serial eeprom interface is enabled (mad[7] low), this register is automatically loaded at power-up from the external serial eeprom and will contain the value downloaded from the serial eeprom or a value of 0x0000 if the download fails. if the external serial eeprom interface is disabled (mad[7] high), this register returns a value of 0x1000. the 16-bit value that should be stored in the external serial eeprom for this register is the vendors pci vendor id and must be obtained from the pci special interest group (sig). please see section 2.4, serial eeprom interface for more information on downloading a value for this register. 15 0 svid if mad[7] is high 0001000000000000 if mad[7] is low xxxxxxxxxxxxxxxx
4-12 registers registers: 0x2eC0x2f subsystem id read only sid subsystem id [15:0] this 16-bit register is used to uniquely identify the add-in board or subsystem where this pci device resides. it provides a mechanism for an add-in card vendor to distinguish its cards from one another even if the cards have the same pci controller installed on them (and therefore the same vendor id and device id). if the external serial eeprom interface is enabled (mad[7] is low), this register is automatically loaded at power-up from the external serial eeprom and will contain the value downloaded from the serial eeprom or a value of 0x0000 if the download fails. if the external serial eeprom is disabled (mad[7] pulled high), the register returns a value of 0x1000. the 16-bit value that should be stored in the external serial eeprom is vendor speci?c. please see section 2.4, serial eeprom interface for additional information on downloading a value for this register. registers: 0x30C0x33 expansion rom base address read/write erba expansion rom base address [31:0] this four-byte register handles the base address and size information for the expansion rom. it functions exactly 15 0 sid if mad[7] is high 0001000000000000 if mad[7] is low xxxxxxxxxxxxxxxx 31 0 erba 00000000000000000000000000000001
pci con?guration registers 4-13 like the base address register zero (i/o) and base address register one (memory) registers, except that the encoding of the bits is different. the upper 21 bits correspond to the upper 21 bits of the expansion rom base address. the expansion rom enable bit, bit 0, is the only bit de?ned in this register. this bit is used to control whether or not the device accepts accesses to its expansion rom. when the bit is set, address decoding is enabled, and a device is used with or without an expansion rom depending on the system con?guration. to access the external memory interface, also set the memory space bit in the command register. the host system detects the size of the external memory by ?rst writing the expansion rom base address register with all ones and then reading back the register. the scsi functions of the SYM53C896 respond with zeros in all dont care locations. the ones in the remaining bits represent the binary version of the external memory size. for example, to indicate an external memory size of 32 kbytes, this register, when written with ones and read back, returns ones in the upper 17 bits. the size of the external memory is set through mad[3:1]. please see section 3.7, mad bus programming for the possible size encodings available. register: 0x34 capabilities pointer read only cp capabilities pointer [7:0] this register indicates that the ?rst extended capability register is located at offset 0x40 in the pci con?guration. registers: 0x35C0x3b reserved 7 0 cp 01000000
4-14 registers register: 0x3c interrupt line read/write il interrupt line [7:0] this register is used to communicate interrupt line routing information. post software writes the routing information into this register as it con?gures the system. the value in this register tells which input of the system interrupt controller(s) the devices interrupt pin is connected to. values in this register are speci?ed by system architecture. register: 0x3d interrupt pin read only ip interrupt pin [7:0] this register is unique to each scsi function. it tells which interrupt pin the device uses. its value is set to 0x01 for the function a (inta/) signal, and 0x02 for the function b (intb/) signal at power-up if mad[4] is pulled low. the function b value is set to 0x01 (inta/) if mad[4] is pulled high. note: please see section 3.7, mad bus programming for additional information. 7 0 il 00000000 7 0 ip scsi function a 00000001 scsi function b if mad[4] pulled low 00000010 scsi function b if mad[4] pulled high 00000001
pci con?guration registers 4-15 register: 0x3e min_gnt read only mg min_gnt [7:0] this register is used to specify the desired settings for latency timer values. min_gnt is used to specify how long a burst period the device needs. the value speci?ed in these registers is in units of 0.25 microseconds. the SYM53C896 sets this register to 0x11. register: 0x3f max_lat read only ml max_lat [7:0] this register is used to specify the desired settings for latency timer values. max_lat is used to specify how often the device needs to gain access to the pci bus. the value speci?ed in these registers is in units of 0.25 microseconds. the SYM53C896 scsi function sets this register to 0x40. 7 0 mg 00010001 7 0 ml 01000000
4-16 registers register: 0x40 capability id read only cid cap_id [7:0] this register indicates the type of data structure currently being used. it is set to 0x01, indicating the power management data structure. register: 0x41 next item pointer read only nip next_item_ptr [7:0] bits [7:0] contain the offset location of the next item in the functions capabilities list. the SYM53C896 has these bits set to zero indicating no further extended capabilities registers exist. registers: 0x42C0x43 power management capabilities (pmc) read only pmes pme_support [15:11] bits [15:11] de?ne the power management states in which the SYM53C896 will assert the pme pin. these bits are all set to zero because the SYM53C896 does not provide a pme signal. 7 0 cid 00000001 7 0 nip 00000000 15 11 10 9 8 6 5 4 3 2 0 pmes d2s d1s auxc dsi r pmec ver[2:0] 00000110000 0 0 010
pci con?guration registers 4-17 d2s d2_support 10 the SYM53C896 sets this bit to indicate support for power management state d2. d1s d1_support 9 the SYM53C896 sets this bit to indicate support for power management state d1. auxc aux_current [8:6] the SYM53C896 always returns zeros. this feature is not supported. dsi device speci?c initialization 5 this bit is cleared to indicate that the SYM53C896 requires no special initialization before the generic class device driver is able to use it. r reserved 4 pmec pme clock 3 bit 3 is cleared because the SYM53C896 does not provide a pme pin. ver[2:0] version [2:0] these three bits are set to 0b010 to indicate that the SYM53C896 complies with revision 1.1 of the pci power management interface speci?cation. registers: 0x44C0x45 power management control/status (pmcsr) read/write pst pme_status 15 the SYM53C896 always returns a zero for this bit, indicating that pme signal generation is not supported from d3cold. dscl[1:0] data_scale [14:13] the SYM53C896 does not support the data register. therefore, these two bits are always cleared. 15 14 13 12 9 8 7 2 0 pst dscl[1:0] dslt[3:0] pen r pws[1:0] 0 0 00000 0 x x x x x x00
4-18 registers dslt[3:0] data_select [12:9] the SYM53C896 does not support the data register. therefore, these four bits are always cleared. pen pme_enable 8 the SYM53C896 always returns zero for this bit to indicate that pme assertion is disabled. r reserved [7:2] pws[1:0] power state [1:0] bits [1:0] are used to determine the current power state of the SYM53C896. they are used to place the SYM53C896 in a new power state. power states are de?ned as: see the section 2.5, power management for descriptions of the power management states. register: 0x46 bridge support extensions (pmcsr_bse) read only bse bridge support extensions [7:0] this register indicates pci bridge speci?c functionality. the SYM53C896 always returns 0x00. 0b00 d0 0b01 d1 0b10 d2 0b11 d3 hot 7 0 bse 00000000
pci con?guration registers 4-19 register: 0x47 data read only data data [7:0] this register provides an optional mechanism for the function to report state-dependent operating data. the SYM53C896 always returns 0x00. 7 0 data 00000000
4-20 registers 4.2 scsi registers the control registers for the scsi core are directly accessible from the pci bus using memory or i/o mapping. each scsi function has the identical register set. the address map of the scsi registers is shown in table 4.2 . note: the only registers that the host cpu can access while the SYM53C896 is executing scripts are the interrupt status zero (istat0) , interrupt status one (istat1) , mailbox zero (mbox0) , and mailbox one (mbox1) registers. attempts to access other registers interfere with the operation of the chip. however, all operating registers are accessible with scripts. all read data is synchronized and stable when presented to the pci bus.
scsi registers 4-21 table 4.2 scsi register map 31 16 15 0 scntl3 scntl2 scntl1 scntl0 0x00 gpreg sdid sxfer scid 0x04 sbcl ssid socl sfbr 0x08 sstat2 sstat1 sstat0 dstat 0x0c dsa 0x10 mbox1 mbox0 istat1 istat0 0x14 ctest3 ctest2 ctest1 ctest0 0x18 temp 0x1c ctest6 ctest5 ctest4 dfifo 0x20 dcmd dbc 0x24 dnad 0x28 dsp 0x2c dsps 0x30 scratch a 0x34 dcntl sbr dien dmode 0x38 adder 0x3c sist1 sist0 sien1 sien0 0x40 gpcntl ctype swide slpar 0x44 respid1 respid0 stime1 stime0 0x48 stest3 stest2 stest1 stest0 0x4c reserved stest4 sidl 0x50 ccntl1 ccntl0 sodl 0x54 reserved sbdl 0x58 scratch b 0x5c scratch cCscratch r 0x60 mmrs 0xa0 mmws 0xa4 sfs 0xa8 drs 0xac sbms 0xb0 dbms 0xb4 dnad64 0xb8 reserved 0xbc pmjad1 0xc0 pmjad2 0xc4 rbc 0xc8 ua 0xcc esa 0xd0 ia 0xd4 reserved sbc 0xd8 csbc 0xdc reserved 0xe0C0xff
4-22 registers register: 0x00 scsi control zero (scntl0) read/write arb[1:0] arbitration mode bits 1 and 0 [7:6] simple arbitration 1. the SYM53C896 scsi function waits for a bus free condition to occur. 2. it asserts sbsy/ and its scsi id (contained in the scsi chip id (scid) register) onto the scsi bus. if the ssel/ signal is asserted by another scsi device, the SYM53C896 scsi function deasserts sbsy/, deasserts its id and sets the lost arbitration bit (bit 3) in the scsi status zero (sstat0) register. 3. after an arbitration delay, the cpu should read the scsi bus data lines (sbdl) register to check if a higher priority scsi id is present. if no higher priority id bit is set, and the lost arbitration bit is not set, the SYM53C896 scsi function wins arbitration. 4. once the SYM53C896 scsi function wins arbitration, ssel/ must be asserted using the scsi output control latch (socl) for a bus clear plus a bus settle delay (1.2 m s) before a low level selection is performed. 76543210 arb[1:0] start watn epc r aap trg 11000 x00 arb1 arb0 arbitration mode 0 0 simple arbitration 0 1 reserved 1 0 reserved 1 1 full arbitration, selection/reselection
scsi registers 4-23 full arbitration, selection/reselection 1. the SYM53C896 scsi function waits for a bus free condition. 2. it asserts sbsy/ and its scsi id (the highest priority id stored in the scsi chip id (scid) register) onto the scsi bus. 3. if the ssel/ signal is asserted by another scsi device or if the SYM53C896 scsi function detects a higher priority id, the SYM53C896 scsi function deasserts sbsy, deasserts its id, and waits until the next bus free state to try arbitration again. 4. the SYM53C896 scsi function repeats arbitration until it wins control of the scsi bus. when it wins, the won arbitration bit is set in the scsi status zero (sstat0) register, bit 2. 5. the SYM53C896 scsi function performs selection by asserting the following onto the scsi bus: ssel/, the targets id (stored in the scsi destination id (sdid) register), and the SYM53C896s id (stored in the scsi chip id (scid) register). 6. after a selection is complete, the function complete bit is set in the scsi interrupt status zero (sist0) register, bit 6. 7. if a selection time-out occurs, the selection time-out bit is set in the scsi interrupt status one (sist1) register, bit 2. start start sequence 5 when this bit is set, the SYM53C896 starts the arbitration sequence indicated by the arbitration mode bits. the start sequence bit is accessed directly in low level mode. during scsi scripts operations, this bit is controlled by the scripts processor. do not start an arbitration sequence if the connected (con) bit in the scsi control one (scntl1) register, bit 4, indicates that the SYM53C896 is already connected to the scsi bus. this bit is automatically cleared when the arbitration sequence is complete. if a sequence is aborted, check bit 4 in the scntl1 register to verify that the SYM53C896 is not connected to the scsi bus.
4-24 registers watn select with satn/ on a start sequence 4 when this bit is set and the SYM53C896 scsi function is in the initiator mode, the satn/ signal is asserted during selection of a scsi target device. this is to inform the target that the SYM53C896 scsi function has a message to send. if a selection time-out occurs while attempting to select a target device, satn/ is deasserted at the same time ssel/ is deasserted. when this bit is cleared, the satn/ signal is not asserted during selection. when executing scsi scripts, this bit is controlled by the scripts processor, but manual setting is possible in low level mode. epc enable parity checking 3 when this bit is set, the scsi data bus is checked for odd parity when data is received from the scsi bus in either the initiator or target mode. if a parity error is detected, bit 0 of the scsi interrupt status zero (sist0) register is set and an interrupt may be generated. if the SYM53C896 scsi function is operating in the initiator mode and a parity error is detected, assertion of satn/ is optional, but the transfer continues until the target changes phase. when this bit is cleared, parity errors are not reported. r reserved 2 aap assert satn/ on parity error 1 when this bit is set, the SYM53C896 scsi function automatically asserts the satn/ signal upon detection of a parity error. satn/ is only asserted in the initiator mode. the satn/ signal is asserted before deasserting sack/ during the byte transfer with the parity error. also set the enable parity checking bit for the SYM53C896 scsi function to assert satn/ in this manner. a parity error is detected on data received from the scsi bus. if the assert satn/ on parity error bit is cleared or the enable parity checking bit is cleared, satn/ is not automatically asserted on the scsi bus when a parity error is received. trg target mode 0 this bit determines the default operating mode of the SYM53C896 scsi function. the user must manually set
scsi registers 4-25 the target or initiator mode. this is done using the scripts language ( set target or clear target ). when this bit is set, the chip is a target device by default. when this bit is cleared, the SYM53C896 scsi function is an initiator device by default. caution: writing this bit while not connected may cause the loss of a selection or reselection due to the changing of target or initiator modes. register: 0x01 scsi control one (scntl1) read/write exc extra clock cycle of data setup 7 when this bit is set, an extra clock period of data setup is added to each scsi data transfer. the extra data setup time can provide additional system design margin, though it affects the scsi transfer rates. clearing this bit disables the extra clock cycle of data setup time. setting this bit only affects scsi send operations. adb assert scsi data bus 6 when this bit is set, the SYM53C896 scsi function drives the contents of the scsi output data latch (sodl) register onto the scsi data bus. when the SYM53C896 scsi function is an initiator, the scsi i/o signal must be inactive to assert the sodl contents onto the scsi bus. when the SYM53C896 scsi function is a target, the scsi i/o signal must be active to assert the sodl con- tents onto the scsi bus. the contents of the sodl reg- ister can be asserted at any time, even before the SYM53C896 scsi function is connected to the scsi bus. clear this bit when executing scsi scripts. it is nor- mally used only for diagnostic testing or operation in low level mode. 76543210 exc adb dhp con rst aesp iarb sst 00000000
4-26 registers dhp disable halt on parity error or atn (target only) 5 the dhp bit is only de?ned for the target mode. when this bit is cleared, the SYM53C896 scsi function halts the scsi data transfer when a parity error is detected or when the satn/ signal is asserted. if satn/ or a parity error is received in the middle of a data transfer, the SYM53C896 scsi function may transfer up to three additional bytes before halting to synchronize between internal core cells. during synchronous operation, the SYM53C896 scsi function transfers data until there are no outstanding synchronous offsets. if the SYM53C896 scsi function is receiving data, any data residing in the dma fifo is sent to memory before halting. when this bit is set, the SYM53C896 scsi function does not halt the scsi transfer when satn/ or a parity error is received. con connected 4 this bit is automatically set any time the SYM53C896 scsi function is connected to the scsi bus as an initiator or as a target. it is set after the SYM53C896 scsi function successfully completes arbitration or when it has responded to a bus initiated selection or reselection. this bit is also set after the chip wins simple arbitration when operating in low level mode. when this bit is cleared, the SYM53C896 scsi function is not connected to the scsi bus. the cpu can force a connected or disconnected condition by setting or clearing this bit. this feature is used primarily during loopback mode. rst assert scsi rst/ signal 3 setting this bit asserts the srst/ signal. the srst/ output remains asserted until this bit is cleared. the 25 m s minimum assertion time de?ned in the scsi speci?cation must be timed out by the controlling microprocessor or a scripts loop. aesp assert even scsi parity (force bad parity) 2 when this bit is set, the SYM53C896 scsi function asserts even parity. it forces a scsi parity error on each byte sent to the scsi bus from the chip. if parity checking is enabled, then the SYM53C896 scsi function checks
scsi registers 4-27 data received for odd parity. this bit is used for diagnostic testing and is cleared for normal operation. it is useful to generate parity errors to test error handling functions. iarb immediate arbitration 1 setting this bit causes the scsi core to immediately begin arbitration once a bus free phase is detected following an expected scsi disconnect. this bit is useful for multithreaded applications. the arb[1:0] bits in scsi control zero (scntl0) are set for full arbitration and selection before setting this bit. arbitration is retried until won. at that point, the SYM53C896 scsi function holds sbsy and ssel asserted, and waits for a select or reselect sequence. the immediate arbitration bit is cleared automatically when the selection or reselection sequence is completed, or times out. an unexpected disconnect condition clears iarb with it attempting arbitration. see the scsi disconnect unexpected bit ( scsi control two (scntl2) , bit 7) for more information on expected versus unexpected disconnects. it is possible to abort an immediate arbitration sequence. first, set the abort bit in the interrupt status zero (istat0) register. then one of two things eventually happens: the won arbitration bit ( scsi status zero (sstat0) bit 2) will be set. in this case, the immediate arbitration bit needs to be cleared. this completes the abort sequence and disconnects the chip from the scsi bus. if it is not acceptable to go to bus free phase immediately following the arbitration phase, it is pos- sible to perform a low level selection instead. the abort completes because the SYM53C896 scsi function loses arbitration. this is detected by the clearing of the immediate arbitration bit. do not use the lost arbitration bit ( scsi status zero (sstat0) bit 3) to detect this condition. in this case take no further action. sst start scsi transfer 0 this bit is automatically set during scripts execution and should not be used. it causes the scsi core to begin a scsi transfer, including sreq/ and sack/ handshaking. the determination of whether the transfer
4-28 registers is a send or receive is made according to the value written to the i/o bit in scsi output control latch (socl) . this bit is self-clearing. do not set it for low level operation. caution: writing to this register while not connected may cause the loss of a selection/reselection by clearing the connected bit. register: 0x02 scsi control two (scntl2) read/write sdu scsi disconnect unexpected 7 this bit is valid in the initiator mode only. when this bit is set, the scsi core is not expecting the scsi bus to enter the bus free phase. if it does, an unexpected disconnect error is generated (see the unexpected disconnect bit in the scsi interrupt status zero (sist0) register, bit 2). dur- ing normal scripts mode operation, this bit is set auto- matically whenever the scsi core is reselected, or successfully selects another scsi device. the sdu bit should be cleared with a register write (move 0x00 to scsi control two (scntl2) ) before the scsi core expects a disconnect to occur, normally prior to sending an abort, abort tag, bus device reset, clear queue or release recovery message, or before deasserting sack/ after receiving a disconnect command or command complete message. chm chained mode 6 this bit determines whether or not the scsi core is programmed for chained scsi mode. this bit is automatically set by the chained block move (chmov) scripts instruction and is automatically cleared by the block move scripts instruction (move). chained mode is primarily used to transfer consecutive wide data blocks. using chained mode facilitates partial receive transfers and allows correct partial send behavior. 76543210 sdu chm slpmd slphben wss vue0 vue1 wsr 00000000
scsi registers 4-29 when this bit is set and a data transfer ends on an odd byte boundary, the SYM53C896 scsi function stores the last byte in the scsi wide residue (swide) register during a receive operation, or in the scsi output data latch (sodl) register during a send operation. this byte is combined with the ?rst byte from the subsequent transfer so that a wide transfer is completed. slpmd slpar mode 5 if this bit is cleared, the scsi longitudinal parity (slpar) register functions as a byte-wide longitudinal parity register. if this bit is set, the slpar functions as a word-wide longitudinal parity function. the high or low byte of the slpar word is accessible through the slpar register. which byte is accessible is controlled by the slphben bit. slphben slpar high byte enable 4 if this bit is cleared, the low byte of the slpar word is accessible through the scsi longitudinal parity (slpar) register. if this bit is set, the high byte of the slpar word is present in the slpar register. wss wide scsi send 3 when read, this bit returns the value of the wide scsi send (wss) ?ag. asserting this bit clears the wss ?ag. this clearing function is self-clearing. when the wss ?ag is high following a wide scsi send operation, the scsi core is holding a byte of chain data in the scsi output data latch (sodl) register. this data becomes the ?rst low-order byte sent when married with a high-order byte during a subsequent data send transfer. performing a scsi receive operation clears this bit. also, performing any nonwide transfer clears this bit. vue0 vendor unique enhancements, bit 0 2 this bit is a read only value indicating whether the group code ?eld in the scsi instruction is standard or vendor unique. if cleared, the bit indicates standard group codes; if set, the bit indicates vendor unique group codes. the value in this bit is reloaded at the beginning of all asynchronous target receives.
4-30 registers vue1 vendor unique enhancement, bit 1 1 this bit is used to disable the automatic byte count reload during block move instructions in the command phase. if this bit is cleared, the device reloads the block move byte count if the ?rst byte received is one of the standard group codes. if this bit is set, the device does not reload the block move byte count, regardless of the group code. wsr wide scsi receive 0 when read, this bit returns the value of the wide scsi receive (wsr) ?ag. setting this bit clears the wsr ?ag. this clearing function is self-clearing. the wsr ?ag indicates that the scsi core received data from the scsi bus, detected a possible partial transfer at the end of a chained or nonchained block move command, and temporarily stored the high-order byte in the scsi wide residue (swide) register rather than passing the byte out the dma channel. the hardware uses the wsr status ?ag to determine what behavior must occur at the start of the next data receive transfer. when the ?ag is set, the stored data in swide may be residue data, valid data for a subsequent data transfer, or overrun data. the byte is read as normal data by starting a data receive transfer. performing a scsi send operation clears this bit. also, performing any nonwide transfer clears this bit. register: 0x03 scsi control three (scntl3) read/write use ultra scsi enable 7 setting this bit enables ultra scsi or ultra2 scsi synchronous transfers. the default value of this bit is 0. this bit should remain cleared if the SYM53C896 is not operating in ultra scsi mode or faster. when this bit is set, the signal ?ltering period for sreq/ and sack/ automatically changes to 8 ns for ultra2 scsi 76 432 0 use scf[2:0] ews ccf[2:0] 00000000
scsi registers 4-31 or 15 ns for ultra scsi, regardless of the value of the extend req/ack filtering bit in the scsi test two (stest2) register. note: set this bit to achieve ultra scsi transfer rates in legacy systems that use an 80 mhz clock. scf[2:0] synchronous clock conversion factor [6:4] these bits select a factor by which the frequency of sclk is divided before being presented to the synchronous scsi control logic. write these to the same value as the clock conversion factor bits below unless fast scsi operation is desired. see the scsi transfer (sxfer) register description for examples of how the scf bits are used to calculate synchronous transfer periods. see the table under the description of bits [7:5] of the sxfer register for the valid combinations. ews enable wide scsi 3 when this bit is cleared, all information transfer phases are assumed to be eight bits, transmitted on sd[7:0]/ and sdp0/. when this bit is asserted, data transfers are done 16 bits at a time, with the least signi?cant byte on sd[7:0]/ and sdp0/ and the most signi?cant byte on sd[15:8]/, sdp1/. command, status, and message phases are not affected by this bit. ccf[2:0] clock conversion factor [2:0] these bits select a factor by which the frequency of sclk is divided before being presented to the scsi core. the synchronous portion of the scsi core can be run at a different clock rate for fast scsi, using the synchronous clock conversion factor bits. the bit encoding is displayed in the table below. all other combinations are reserved.
4-32 registers note: it is important that these bits are set to the proper values to guarantee that the SYM53C896 meets the scsi timings as de?ned by the ansi speci?cation. register: 0x04 scsi chip id (scid) read/write r reserved 7 rre enable response to reselection 6 when this bit is set, the SYM53C896 scsi function is enabled to respond to bus-initiated reselection at the chip id in the response id zero (respid0) and response id one (respid1) registers. note that the chip does not automatically recon?gure itself to the initiator mode as a result of being reselected. sre enable response to selection 5 when this bit is set, the SYM53C896 scsi function is able to respond to bus-initiated selection at the chip id in the response id zero (respid0) and response id one (respid1) registers. note that the chip does not automatically recon?gure itself to target mode as a result of being selected. scf2 ccf2 scf1 ccf1 scf0 ccf0 factor frequency scsi clock (mhz) 0 0 0 sclk/3 50.01C75.0 0 0 1 sclk/1 16.67C25.0 0 1 0 sclk/1.5 25.01C37.5 0 1 1 sclk/2 37.51C50.0 1 0 0 sclk/3 50.01C75.0 1 0 1 sclk/4 75.01C80.00 1 1 0 sclk/6 120 1 1 1 sclk/8 160 76543 0 r rre sre r enc[3:0] x00 x0000
scsi registers 4-33 r reserved 4 enc[3:0] encoded chip scsi id [3:0] these bits are used to store the SYM53C896 scsi function encoded scsi id. this is the id which the chip asserts when arbitrating for the scsi bus. the ids that the SYM53C896 scsi function responds to when selected or reselected are con?gured in the response id zero (respid0) and response id one (respid1) registers. the priority of the 16 possible ids, in descending order is: register: 0x05 scsi transfer (sxfer) read/write note: when using table indirect i/o commands, bits [7:0] of this register are loaded from the i/o data structure. tp[2:0] scsi synchronous transfer period [7:5] these bits determine the scsi synchronous transfer period used by the SYM53C896 scsi function when sending synchronous scsi data in either the initiator or target mode. these bits control the programmable dividers in the chip. highest lowest 7654321015141312111098 754 0 tp[2:0] mo[4:0] 00000000
4-34 registers the synchronous transfer period the SYM53C896 should use when transferring scsi data is determined in the following example: the SYM53C896 is connected to a hard disk which can transfer data at 10 mbytes/s synchronously. the SYM53C896 scsi functions sclk is running at 40 mhz. the synchronous transfer period (sxferp) is found as follows: sxferp = period/sscp + extcc period = 1 ? frequency = 1 ? 10 mbytes/s = 100 ns sscp = 1 ? sscf = 1 ? 40 mhz = 25 ns (this scsi synchronous core clock is determined in scntl3 bits [6:4], extcc = 1 if scntl1 bit 7 is asserted and the SYM53C896 is sending data. extcc = 0 if the SYM53C896 is receiving data.) sxferp = 100 ? 25=4 where tp2 tp1 tp0 xferp 0004 0015 0106 0117 1008 1019 11010 11111 sxferp synchronous transfer period sscp scsi synchronous core period sscf scsi synchronous core frequency extcc extra clock cycle of data setup
scsi registers 4-35 table 4.3 examples of synchronous transfer periods and rates for scsi-1 clk (mhz) scsi clk ? scntl3 bits [6:4] xferp synch. transfer period (ns) synch. transfer rate (mbytes) 66.67 3 4 180 5.55 66.67 3 5 225 4.44 50 2 4 160 6.25 5 2 5 200 5 40 4 4 200 5 37.50 1.5 4 160 6.25 33.33 1.5 4 180 5.55 25 1 4 160 6.25 20 1 4 200 5 16.67 1 4 240 4.17 table 4.4 example transfer periods and rates for fast scsi-2, ultra and ultra2 clk (mhz) scsi clk ? scntl3 bits [6:4] xferp synch. transfer period (ns) synch. transfer rate (mbytes) 160 1 4 25 40 160 2 4 50 20 160 4 4 100 10 80 1 4 50 20 50 1 4 80 12.5 50 1 4 100 10.0 40 1 4 100 10.0 37.50 1 4 106.67 9.375 33.33 1 4 120 8.33 25 1 4 160 6.25 20 1 4 200 5 16.67 1 4 240 4.17
4-36 registers mo[4:0] max scsi synchronous offset [4:0] these bits describe the maximum scsi synchronous offset used by the SYM53C896 scsi function when transferring synchronous scsi data in either the initiator or target mode. the following table describes the possible combinations and their relationship to the synchronous data offset used by the SYM53C896 scsi function. these bits determine the SYM53C896 scsi functions method of transfer for data in and data out phases only. all other information transfers occur asynchronously.
scsi registers 4-37 table 4.5 maximum synchronous offset mo4 mo3 mo2 mo1 mo0 synchronous offset 00000 0-asynchronous 00001 1 00010 2 00011 3 00100 4 00101 5 00110 6 00111 7 01000 8 01001 9 01010 10 01011 11 01100 12 01101 13 01110 14 01111 15 10000 16 10001 17 10010 18 10011 19 10100 20 10101 21 10110 22 10111 23 11000 24 11001 25 11010 26 11011 27 11100 28 11101 29 11110 30 11111 31
4-38 registers register: 0x06 scsi destination id (sdid) read/write r reserved [7:4] enc[3:0] encoded destination scsi id [3:0] writing these bits sets the scsi id of the intended initiator or target during scsi reselection or selection phases, respectively. when executing scripts, the scripts processor writes the destination scsi id to this register. the scsi id is de?ned by the user in a scripts select or reselect instruction. the value written is the binary-encoded id. the priority of the 16 possible ids, in descending order, is: register: 0x07 general purpose (gpreg) read/write this register complements the gpreg register in the other scsi function. any reads or writes to either of these registers have the same effect, and are re?ected in both registers. reads to these two registers will always yield the same values. a write to this register will cause the data written to be output to the appropriate gpio pin if it is set to output mode in that functions general purpose pin control (gpcntl) register. behavior of gpio pins, if set to output mode by both functions, is unde?ned. 7430 r enc[3:0] x x x x0000 highest lowest 7654321015141312111098 754 0 r gpio x x x0xxxx
scsi registers 4-39 r reserved [7:5] gpio general purpose i/o [4:0] these bits are programmed through the general purpose pin control (gpcntl) register as inputs, outputs, or to perform special functions. as an output, these pins can be used to enable or disable external terminators. it is also possible to program these signals as live inputs and sense them through a scripts register to register move instruction. gpio[3:0] default as inputs and gpio4 defaults as an output pin. when con?gured as inputs, an internal pull-down is enabled. lsi logic symbios software uses the gpio[1:0] signals to access serial eeprom. gpio1 is used as a clock, with the gpio0 pin serving as data. lsi logic symbios software also reserves the use of gpio[4:2]. if there is a need to use gpio[4:2], please check with lsi logic for additional information. register: 0x08 scsi first byte received (sfbr) read/write this register contains the ?rst byte received in any asynchronous information transfer phase. for example, when a SYM53C896 scsi function is operating in the initiator mode, this register contains the ?rst byte received in the message-in, status, and data-in phases. when a block move instruction is executed for a particular phase, the ?rst byte received is stored in this register - even if the present phase is the same as the last phase. the ?rst byte received value for a particular input phase is not valid until after a move instruction is executed. this register is also the accumulator for register read-modify-writes with the scsi first byte received (sfbr) as the destination. this allows bit testing after an operation. 7 0 ib 00000000
4-40 registers the scsi first byte received (sfbr) is not writable using the cpu, and therefore not by a memory move. however, it can be loaded using scripts read/write operations. to load the sfbr with a byte stored in system memory, the byte must ?rst be moved to an intermediate SYM53C896 scsi function register (such as the scratch register), and then to the sfbr. this register also contains the state of the lower eight bits of the scsi data bus during the selection phase if the com bit in the dma control (dcntl) register is clear. if the com bit is cleared, do not access this register using scripts operations, as nondeterminate operations may occur. (this includes scripts read/write operations and conditional transfer control instructions that initialize the scsi first byte received (sfbr) register.) register: 0x09 scsi output control latch (socl) read/write req assert scsi req/ signal 7 ack assert scsi ack/ signal 6 bsy assert scsi bsy/ signal 5 sel assert scsi sel/ signal 4 atn assert scsi atn/ signal 3 msg assert scsi msg/ signal 2 c_d assert scsi c_d/ signal 1 i/o assert scsi i_o/ signal 0 this register is used primarily for diagnostic testing or programmed i/o operation. it is controlled by the scripts processor when executing scsi scripts. scsi output control latch (socl) is used only when transferring data using programmed i/o. some bits are set or cleared 76543210 req ack bsy sel atn msg c_d i/o 00000000
scsi registers 4-41 when executing scsi scripts. do not write to the register once the SYM53C896 scsi function starts executing normal scsi scripts. register: 0x0a scsi selector id (ssid) read only val scsi valid 7 if val is asserted, then the two scsi ids are detected on the bus during a bus-initiated selection or reselection, and the encoded destination scsi id bits below are valid. if val is deasserted, only one id is present and the contents of the encoded destination id are meaningless. r reserved [6:4] enid encoded destination scsi id [3:0] reading the scsi selector id (ssid) register immediately after the SYM53C896 scsi function is selected or reselected returns the binary-encoded scsi id of the device that performed the operation. these bits are invalid for targets that are selected under the single initiator option of the scsi-1 speci?cation. this condition is detected by examining the val bit. 76 43 0 val r enid 0 0 0 00000
4-42 registers register: 0x0b scsi bus control lines (sbcl) read only req assert scsi req/ signal 7 ack assert scsi ack/ signal 6 bsy assert scsi bsy/ signal 5 sel assert scsi sel/ signal 4 atn assert scsi atn/ signal 3 msg assert scsi msg/ signal 2 c_d assert scsi c_d/ signal 1 i_o assert scsi i_o/ signal 0 this register returns the scsi control line status. a bit is set when the corresponding scsi control line is asserted. these bits are not latched; they are a true representation of what is on the scsi bus at the time the register is read. the resulting read data is synchronized before being presented to the pci bus to prevent parity errors from being passed to the system. this register is used for diagnostic testing or operation in the low level mode. register: 0x0c dma status (dstat) read only reading this register clears any bits that are set at the time the register is read, but does not necessarily clear the register in case additional interrupts are pending (the SYM53C896 scsi functions stack interrupts). 76543210 req ack bsy sel atn msg c_d i_o xxxxxxxx 76543210 dfe mdpe bf abrt ssi sir r iid 100000 x0
scsi registers 4-43 the dip bit in the interrupt status zero (istat0) register is also cleared. it is possible to mask dma interrupt conditions individually through the dma interrupt enable (dien) register. when performing consecutive 8-bit reads of the dma status (dstat) , scsi interrupt status zero (sist0) and scsi interrupt status one (sist1) registers (in any order), insert a delay equivalent to 12 clk periods between the reads to ensure that the interrupts clear properly. see chapter 2, functional description for more information on interrupts. dfe dma fifo empty 7 this status bit is set when the dma fifo is empty. it is possible to use it to determine if any data resides in the fifo when an error occurs and an interrupt is generated. this bit is a pure status bit and does not cause an interrupt. mdpe master data parity error 6 this bit is set when the SYM53C896 scsi function as a master detects a data parity error, or a target device signals a parity error during a data phase. this bit is completely disabled by the master parity error enable bit (bit 3 of chip test four (ctest4) ). bf bus fault 5 this bit is set when a pci bus fault condition is detected. a pci bus fault can only occur when the SYM53C896 scsi function is bus master, and is de?ned as a cycle that ends with a bad address or target abort condition. abrt aborted 4 this bit is set when an abort condition occurs. an abort condition occurs when a software abort command is issued by setting bit 7 of the interrupt status zero (istat0) register. ssi single step interrupt 3 if the single step mode bit in the dma control (dcntl) register is set, this bit is set and an interrupt generated after successful execution of each scripts instruction. sir scripts interrupt instruction received 2 this status bit is set whenever an interrupt instruction is evaluated as true.
4-44 registers r reserved 1 iid illegal instruction detected 0 this status bit is set any time an illegal or reserved instruction opcode is detected, whether the SYM53C896 scsi function is operating in single step mode or automatically executing scsi scripts. any of the following conditions during instruction execution also sets this bit: the SYM53C896 scsi function is executing a wait disconnect instruction and the scsi req line is asserted without a disconnect occurring. a block move instruction is executed with 0x000000 loaded into the dma byte counter (dbc) register, indicating there are zero bytes to move. during a transfer control instruction, the compare data (bit 18) and compare phase (bit 17) bits are set in the dma byte counter (dbc) register while the SYM53C896 scsi function is in target mode. during a transfer control instruction, the carry test bit (bit 21) is set and either the compare data (bit 18) or compare phase (bit 17) bit is set. a transfer control instruction is executed with the reserved bit 22 set. a transfer control instruction is executed with the wait for valid phase bit (bit 16) set while the chip is in target mode. a load/store instruction is issued with the memory address mapped to the operating registers of the chip, not including rom or ram. a load/store instruction is issued when the register address is not aligned with the memory address. a load/store instruction is issued with bit 5 in the dma command (dcmd) register cleared or bits 3 or 2 set. a load/store instruction when the count value in the dma byte counter (dbc) register is not set at 1 to 4. a load/store instruction attempts to cross a dword boundary.
scsi registers 4-45 a memory move instruction is executed with one of the reserved bits in the dma command (dcmd) register set. a memory move instruction is executed with the source and destination addresses not aligned. register: 0x0d scsi status zero (sstat0) read only ilf sidl least signi?cant byte full 7 this bit is set when the least signi?cant byte in the scsi input data latch (sidl) contains data. data is transferred from the scsi bus to the scsi input data latch register before being sent to the dma fifo and then to the host bus. the scsi input data latch (sidl) register contains scsi data received asynchronously. synchronous data received does not ?ow through this register. orf sodr least signi?cant byte full 6 this bit is set when the least signi?cant byte in the scsi output data register (sodr, a hidden buffer register which is not accessible) contains data. the sodr is used by the scsi logic as a second storage register when sending data synchronously. it is not readable or writable by the user. it is possible to use this bit to determine how many bytes reside in the chip when an error occurs. olf sodl least signi?cant byte full 5 this bit is set when the least signi?cant byte in the scsi output data latch (sodl) contains data. the sodl register is the interface between the dma logic and the scsi bus. in synchronous mode, data is transferred from the host bus to the scsi output data latch (sodl) register, and then to the scsi output data register (sodr, a hidden buffer register which is not accessible) before being sent to the scsi bus. in asynchronous mode, data is transferred from the host bus to the sodl 76543210 ilf orf olf aip loa woa rst sdp0 00000000
4-46 registers register, and then to the scsi bus. the sodr buffer register is not used for asynchronous transfers. it is possible to use this bit to determine how many bytes reside in the chip when an error occurs. aip arbitration in progress 4 arbitration in progress (aip = 1) indicates that the SYM53C896 scsi function has detected a bus free condition, asserted sbsy, and asserted its scsi id onto the scsi bus. loa lost arbitration 3 when set, loa indicates that the SYM53C896 scsi function has detected a bus free condition, arbitrated for the scsi bus, and lost arbitration due to another scsi device asserting the ssel/ signal. woa won arbitration 2 when set, woa indicates that the SYM53C896 scsi function has detected a bus free condition, arbitrated for the scsi bus and won arbitration. the arbitration mode selected in the scsi control zero (scntl0) register must be full arbitration and selection to set this bit. rst scsi rst/ signal 1 this bit reports the current status of the scsi rst/ signal, and the rst signal (bit 3) in the scsi control one (scntl1) register. this bit is not latched and may change as it is read. sdp0 scsi sdp0 parity signal 0 this bit represents the present state of the scsi sdp0/ parity signal. this signal is not latched and may change as it is read.
scsi registers 4-47 register: 0x0e scsi status one (sstat1) read only ff[3:0] fifo flags [7:4] these four bits, along with scsi status two (sstat2) bit 4, de?ne the number of bytes or words that currently reside in the SYM53C896s scsi synchronous data fifo. these bits are not latched and they will change as data moves through the fifo. 7 43210 ff[3:0] sdp0l msg c_d i/o 0000xxxx
4-48 registers table 4.6 scsi synchronous data fifo word count ff4 (sstat2 bit 4) ff3 ff2 ff1 ff0 bytes or words in the scsi fifo 000000 000011 000102 000113 001004 001015 001106 001117 010008 010019 0101010 0101111 0110012 0110113 0111014 0111115 1000016 1000117 1001018 1001119 1010020 1010121 1011022 1011123 1100024 1100125 1101026 1101127 1110028 1110129 1111030 1111131
scsi registers 4-49 sdp0l latched scsi parity 3 this bit re?ects the scsi parity signal (sdp0/), corresponding to the data latched in the scsi input data latch (sidl) . it changes when a new byte is latched into the least signi?cant byte of the sidl register. this bit is active high, in other words, it is set when the parity signal is active. msg scsi msg/ signal 2 c_d scsi c_d/ signal 1 i/o scsi i_o/ signal 0 these scsi phase status bits are latched on the asserting edge of sreq/ when operating in either the initiator or target mode. these bits are set when the corresponding signal is active. they are useful when operating in the low level mode. register: 0x0f scsi status two (sstat2) read only ilf sidl most signi?cant byte full 7 this bit is set when the most signi?cant byte in the scsi input data latch (sidl) contains data. data is transferred from the scsi bus to the scsi input data latch register before being sent to the dma fifo and then to the host bus. the sidl register contains scsi data received asynchronously. synchronous data received does not ?ow through this register. orf1 sodr most signi?cant byte full 6 this bit is set when the most signi?cant byte in the scsi output data register (sodr, a hidden buffer register which is not accessible) contains data. the sodr register is used by the scsi logic as a second storage register when sending data synchronously. it is not accessible to the user. this bit is used to determine how many bytes reside in the chip when an error occurs. 76543210 ilf orf1 olf1 ff4 spl1 diff ldsc sdp1 0000xx1x
4-50 registers olf1 sodl most signi?cant byte full 5 this bit is set when the most signi?cant byte in the scsi output data latch (sodl) contains data. the sodl register is the interface between the dma logic and the scsi bus. in synchronous mode, data is transferred from the host bus to the sodl register, and then to the scsi output data register (sodr, a hidden buffer register which is not accessible) before being sent to the scsi bus. in asynchronous mode, data is transferred from the host bus to the scsi output data latch (sodl) register, and then to the scsi bus. the sodr buffer register is not used for asynchronous transfers. it is possible to use this bit to determine how many bytes reside in the chip when an error occurs. ff4 fifo flags, bit 4 4 this is the most signi?cant bit in the scsi fifo flags ?eld, with the rest of the bits in scsi status one (sstat1) . for a complete description of this ?eld, see the de?nition for s s tat 1 bits [7:4]. spl1 latched scsi parity for sd[15:8] 3 this active high bit re?ects the scsi odd parity signal corresponding to the data latched into the most signi?cant byte in the scsi input data latch (sidl) register. diff diffsens mismatch 2 this bit is set when the diffsens pin detects a se or lvd scsi operating voltage level while the SYM53C896 is operating in hvd mode (by setting the dif bit in the scsi test two (stest2) register). if this bit is cleared, the diffsens value matches the dif bit setting. ldsc last disconnect 1 this bit is used in conjunction with the connected (con) bit in scsi control one (scntl1) . it allows the user to detect the case in which a target device disconnects, and then some scsi device selects or reselects the SYM53C896 scsi function. if the connected bit is asserted and the ldsc bit is asserted, a disconnect is indicated. this bit is set when the connected bit in scntl1 is off. this bit is cleared when a block move instruction is executed while the connected bit in scntl1 is on.
scsi registers 4-51 sdp1 scsi sdp1 parity signal 0 this bit represents the present state of the scsi sdp1/ parity signal. it is unlatched and may change as it is read. registers: 0x10C0x13 data structure address (dsa) read/write this 32-bit register contains the base address used for all table indirect calculations. the dsa register is usually loaded prior to starting an i/o, but it is possible for a scripts memory move to load the dsa during the i/o. during any memory-to-memory move operation, the contents of this register is preserved. the power-up value of this register is indeterminate. register: 0x14 interrupt status zero (istat0) read/write this is the only register that is accessible by the host cpu while a SYM53C896 scsi function is executing scripts (without interfering in the operation of the function). it is used to poll for interrupts if hardware interrupts are disabled. read this register after servicing an interrupt to check for stacked interrupts. abrt aborted 7 setting this bit aborts the current operation under execution by the SYM53C896 scsi function. if this bit is set and an interrupt is received, clear this bit before reading the dma status (dstat) register to prevent further aborted interrupts from being generated. the sequence to abort any operation is: 1. set this bit. 2. wait for an interrupt. 3. read the interrupt status zero (istat0) register. 76543210 abrt srst sigp sem con intf sip dip 00000000
4-52 registers 4. if the scsi interrupt pending bit is set, then read the scsi interrupt status zero (sist0) or scsi interrupt status one (sist1) register to determine the cause of the scsi interrupt and go back to step 2. 5. if the scsi interrupt pending bit is clear, and the dma interrupt pending bit is set, then write 0x00 value to this register. 6. read the dma status (dstat) register to verify the aborted interrupt and to see if any other interrupting conditions have occurred. srst software reset 6 setting this bit resets the SYM53C896 scsi function. all operating registers are cleared to their respective default values and all scsi signals are deasserted. setting this bit does not assert the scsi rst/ signal. this reset does not clear the id mode bit or any of the pci con?guration registers. this bit is not self-clearing; it must be cleared to clear the reset condition (a hardware reset also clears this bit). sigp signal process 5 sigp is a r/w bit that is writable at any time, and polled and reset using chip test two (ctest2) . the sigp bit is used in various ways to pass a ?ag to or from a running scripts instruction. the only scripts instruction directly affected by the sigp bit is wait for selection/reselection. setting this bit causes that instruction to jump to the alternate address immediately. the instructions at the alternate jump address should check the status of sigp to determine the cause of the jump. the sigp bit is usable at any time and is not restricted to the wait for selection/reselection condition. sem semaphore 4 the scripts processor may set this bit using a scripts register write instruction. an external processor may also set it while the SYM53C896 scsi function is executing a scripts operation. this bit enables the scsi function to notify an external processor of a prede?ned condition while scripts are running. the
scsi registers 4-53 external processor may also notify the SYM53C896 scsi function of a prede?ned condition and the scripts processor may take action while scripts are executing. con connected 3 this bit is automatically set any time the SYM53C896 scsi function is connected to the scsi bus as an initiator or as a target. it is set after successfully completing selection or when the SYM53C896 scsi function responds to a bus-initiated selection or reselection. it is also set after the scsi function wins arbitration when operating in low level mode. when this bit is cleared, the SYM53C896 scsi function is not connected to the scsi bus. intf interrupt-on-the-fly 2 this bit is asserted by an intfly instruction during scripts execution. scripts programs do not halt when the interrupt occurs. this bit can be used to notify a service routine, running on the main processor while the scripts processor is still executing a scripts program. if this bit is set, when the interrupt status zero (istat0) register is read it is not automatically cleared. to clear this bit, write it to a one. the reset operation is self-clearing. note: if the intf bit is set but sip or dip is not set, do not attempt to read the other chip status registers. an interrupt-on-the-?y must be cleared before servicing any other interrupts indicated by sip or dip. this bit must be written to one in order to clear it after it has been set.
4-54 registers sip scsi interrupt pending 1 this status bit is set when an interrupt condition is detected in the scsi portion of the SYM53C896 scsi function. the following conditions cause a scsi interrupt to occur: a phase mismatch (initiator mode) or satn/ becomes active (target mode) an arbitration sequence completes a selection or reselection time-out occurs the SYM53C896 scsi function is selected the SYM53C896 scsi function is reselected a scsi gross error occurs an unexpected disconnect occurs a scsi reset occurs a parity error is detected the handshake-to-handshake timer is expired the general purpose timer is expired to determine exactly which condition(s) caused the interrupt, read the scsi interrupt status zero (sist0) and scsi interrupt status one (sist1) registers. dip dma interrupt pending 0 this status bit is set when an interrupt condition is detected in the dma portion of the SYM53C896 scsi function. the following conditions cause a dma interrupt to occur: a pci parity error is detected a bus fault is detected an abort condition is detected a scripts instruction is executed in single step mode a scripts interrupt instruction is executed an illegal instruction is detected to determine exactly which condition(s) caused the interrupt, read the dma status (dstat) register.
scsi registers 4-55 register: 0x15 interrupt status one (istat1) read/write r reserved [7:3] flsh flushing 2 reading this bit monitors if the chip is currently ?ushing data. if set, the chip is ?ushing data from the dma fifo. if cleared, no ?ushing is occurring. this bit is read only and writes will have no effect on the value of this bit. srun scripts running 1 this bit indicates whether or not the scripts engine is currently fetching and executing scripts instructions. if this bit is set, the scripts engine is active. if it is cleared, the scripts engine is not active. this bit is read only and writes will have no effect on the value of this bit. si sync_irqd 0 setting this bit disables the inta/ pin for function a and the intb/ pin for function b. clearing this bit enables normal operation of the inta/ (or intb/) pin. the function of this bit is nearly identical to bit 1 of dma control (dcntl) (register 0x3b ) except that if the inta/ (or intb/) is already asserted and this bit is set, int will remain asserted until the interrupt is serviced. at this point the interrupt line will be blocked for future interrupts until this bit is cleared. in addition, this bit may be read and written while scripts are executing. 7 3210 r flsh srun si x x x x x000
4-56 registers register: 0x16 mailbox zero (mbox0) read/write mbox0 mailbox zero [7:0] these are general purpose bits that may be read or written while scripts are running. they also may be read or written by the scripts processor. note: the host and the scripts processor code could potentially attempt to access the same mailbox byte at the same time. using one mailbox register as a read only and the other as a write only will prevent this type of con?ict. register: 0x17 mailbox one (mbox1) read/write mbox1 mailbox one [7:0] these are general purpose bits that may be read or written while scripts are running. they also may be read or written by the scripts processor. note: the host and the scripts processor code could potentially attempt to access the same mailbox byte at the same time. using one mailbox register as a read only and the other as a write only will prevent this type of con?ict. 7 0 mbox0 00000000 7 0 mbox1 00000000
scsi registers 4-57 register: 0x18 chip test zero (ctest0) read/write fmt byte empty in dma fifo [7:0] these bits identify the bottom bytes in the dma fifo that are empty. each bit corresponds to a byte lane in the dma fifo. for example, if byte lane three is empty, then fmt3 will be set. since the fmt ?ags indicate the status of bytes at the bottom of the fifo, if all fmt bits are set, the dma fifo is empty. register: 0x19 chip test one (ctest1) read only ffl byte full in dma fifo [7:0] these status bits identify the top bytes in the dma fifo that are full. each bit corresponds to a byte lane in the dma fifo. for example, if byte lane three is full then ffl3 is set. since the ffl ?ags indicate the status of bytes at the top of the fifo, if all ffl bits are set, the dma fifo is full. 7 0 fmt 11111111 7 0 ffl 00000000
4-58 registers register: 0x1a chip test two (ctest2) read only (bit 3 write) ddir data transfer direction 7 this status bit indicates which direction data is being transferred. when this bit is set, the data is transferred from the scsi bus to the host bus. when this bit is clear, the data is transferred from the host bus to the scsi bus. sigp signal process 6 this bit is a copy of the sigp bit in the interrupt status zero (istat0) register (bit 5). the sigp bit is used to signal a running scripts instruction. when this register is read, the sigp bit in the istat0 register is cleared. cio con?gured as i/o 5 this bit is de?ned as the con?guration i/o enable status bit. this read only bit indicates if the chip is currently enabled as i/o space. cm con?gured as memory 4 this bit is de?ned as the con?guration memory enable status bit. this read only bit indicates if the chip is currently enabled as memory space. note: bits 4 and 5 may be set if the chip is mapped in both i/o and memory space. also, bits 4 and 5 may be set if the chip is dual-mapped. pcicie pci con?guration info enable 3 this bit controls the shadowing of the pci base address register two (scripts ram) , pci base address register one (memory), pci device id , and pci revision id (rev id) into the scratch register a (scratcha) , memory move read selector (mmrs) , scratch register b (scratchb) , memory move write selector (mmws) , and scripts fetch selector (sfs) registers. 76543210 ddir sigp cio cm pcicie teop dreq dack 00xx0001
scsi registers 4-59 when it is set, mmws contains bits [63:32] and scratch b contains bits [31:0] of the ram base address value from the pci con?guration base address register two (scripts ram) . this is the base address for the internal 8 kbytes internal ram. memory move read selector (mmrs) contains bits [63:32] and scratch register a (scratcha) contains bits [31:0] of the memory mapped operating register base address. bits [23:16] of scripts fetch selector (sfs) contain the pci revision id (rev id) register value and bits [15:0] contain the pci device id register value. when this bit is set, only reads to the registers are affected, writes will pass through normally. when this bit is cleared, the scratch a, mmrs, scratch b, mmws, and sfs registers return to normal operation. note: bit 3 is the only writable bit in this register. all other bits are read only. when modifying this register, all other bits must be written to zero. do not execute a read-modify-write to this register. teop scsi true end of process 2 this bit indicates the status of the SYM53C896 scsi functions internal teop signal. the teop signal acknowledges the completion of a transfer through the scsi portion of the SYM53C896 scsi function. when this bit is set, teop is active. when this bit is cleared, teop is inactive. dreq data request status 1 this bit indicates the status of the SYM53C896 scsi functions internal data request signal (dreq). when this bit is set, dreq is active. when this bit is cleared, dreq is inactive. dack data acknowledge status 0 this bit indicates the status of the SYM53C896 scsi functions internal data acknowledge signal (dack/). when this bit is set, dack/ is inactive. when this bit is cleared, dack/ is active.
4-60 registers register: 0x1b chip test three (ctest3) read/write v chip revision level [7:4] these bits identify the chip revision level for software purposes. it should have the same value as the lower nibble of the pci revision id (rev id) register. these bits are read only. flf flush dma fifo 3 when this bit is set, data residing in the dma fifo is transferred to memory, starting at the address in the dma next address (dnad) register. the internal dmawr signal, controlled by the chip test five (ctest5) register, determines the direction of the transfer. this bit is not self-clearing; clear it once the data is successfully transferred by the SYM53C896 scsi function. note: polling of fifo ?ags is allowed during ?ush operations. clf clear dma fifo 2 when this bit is set, all data pointers for the dma fifo are cleared. any data in the fifo is lost. after the SYM53C896 scsi function successfully clears the appropriate fifo pointers and registers, this bit automatically clears. note: this bit does not clear the data visible at the bottom of the fifo. fm fetch pin mode 1 when set, this bit causes the fetch/ pin to deassert during indirect and table indirect read operations. fetch/ is only active during the opcode portion of an instruction fetch. this allows the storage of scripts in a prom while data tables are stored in ram. if this bit is not set, fetch/ is asserted for all bus cycles during instruction fetches. 7 43210 v flf clf fm wrie xxxx 0001
scsi registers 4-61 wrie write and invalidate enable 0 this bit, when set, causes the issuing of write and invalidate commands on the pci bus whenever legal. the write and invalidate enable bit in the pci con?guration command register must also be set in order for the chip to generate write and invalidate commands. registers: 0x1cC0x1f temporary (temp) read/write this 32-bit register stores the return instruction address pointer from the call instruction. the address pointer stored in this register is loaded into the dma scripts pointer (dsp) register when a return instruction is executed. this address points to the next instruction to execute. do not write to this register while the SYM53C896 scsi function is executing scripts. during any memory-to-memory move operation, the contents of this register are preserved. the power-up value of this register is indeterminate. register: 0x20 dma fifo (dfifo) read/write bo byte offset counter [7:0] these bits, along with bits [1:0] in the chip test five (ctest5) register, indicate the amount of data transferred between the scsi core and the dma core. it is used to determine the number of bytes in the dma fifo when an interrupt occurs. these bits are unstable while data is being transferred between the two cores. once the chip has stopped transferring data, these bits are stable. the dma fifo (dfifo) register counts the number of bytes transferred between the dma core and the scsi 7 0 bo 00000001
4-62 registers core. the dma byte counter (dbc) register counts the number of bytes transferred across the host bus. the difference between these two counters represents the number of bytes remaining in the dma fifo. the following steps determine how many bytes are left in the dma fifo when an error occurs, regardless of the transfer direction: if the dfs bit (bit 5, chip test five (ctest5) ) is set: step 1. subtract the ten least signi?cant bits of the dma byte counter (dbc) register from the 10-bit value of the dfboc which is made up of the chip test five (ctest5) register (bits [1:0]) and the dma fifo (dfifo) register (bits [7:0]). step 2. and the result with 0x3ff for a byte count between zero and 944. if the dfs bit (bit 5, chip test five (ctest5) ) is cleared: step 1. subtract the seven least signi?cant bits of the dma byte counter (dbc) register from the seven bit value of the dfboc which is made up of the dma fifo (dfifo) register (bits [6:0]). step 2. and the result with 0x7f for a byte count between zero and 112. note: if trying to calculate the total number of bytes in both the dma fifo and scsi logic, see section 2.2.12.1, data paths in chapter 2, functional description . register: 0x21 chip test four (ctest4) read/write bdis burst disable 7 when set, this bit causes the SYM53C896 scsi function to perform back to back cycles for all transfers. when this 765432 0 bdis fbl3 zsd srtm mpee fbl[2:0] 00000000
scsi registers 4-63 bit is cleared, back to back transfers for opcode fetches and burst transfers for data moves are performed. fbl3 fifo byte control 6 this bit is used with fbl[2:0]. see bits [2:0] description in this register. zsd scsi data high impedance 5 setting this bit causes the SYM53C896 scsi function to place the scsi data bus sd[15:0] and the parity lines sdp[1:0] in a high impedance state. in order to transfer data on the scsi bus, clear this bit. srtm shadow register test mode 4 setting this bit allows access to the shadow registers used by memory-to-memory move operations. when this bit is set, register accesses to the temporary (temp) and data structure address (dsa) registers are directed to the shadow copies stemp (shadow temp) and sdsa (shadow dsa). the registers are shadowed to prevent them from being overwritten during a memory-to-memory move operation. the data structure address (dsa) and temporary (temp) registers contain the base address used for table indirect calculations, and the address pointer for a call or return instruction, respectively. this bit is intended for manufacturing diagnostics only and should not be set during normal operations. mpee master parity error enable 3 setting this bit enables parity checking during master data phases. a parity error during a bus master read is detected by the SYM53C896 scsi function. a parity error during a bus master write is detected by the target, and the SYM53C896 scsi function is informed of the error by the perr/ pin being asserted by the target. when this bit is cleared, the SYM53C896 scsi function does not interrupt if a master parity error occurs. this bit is cleared at power-up.
4-64 registers fbl[2:0] fifo byte control [2:0] these bits steer the contents of the chip test six (ctest6) register to the appropriate byte lane of the 64-bit dma fifo. if the fbl3 bit is set, then fbl2 through fbl0 determine which of eight byte lanes can be read or written. when cleared, the byte lane read or written is determined by the current contents of the dma next address (dnad) and dma byte counter (dbc) registers. each of the eight bytes that make up the 64-bit dma fifo is accessed by writing these bits to the proper value. for normal operation, fbl3 must equal zero. register: 0x22 chip test five (ctest5) read/write adck clock address incrementor 7 setting this bit increments the address pointer contained in the dma next address (dnad) register. the dnad register is incremented based on the dnad contents and the current dma byte counter (dbc) value. this bit automatically clears itself after incrementing the dnad register. fbl3 fbl2 fbl1 fbl0 dma fifo byte lane pins 0 x x x disabled n/a 1 0 0 0 0 d[7:0] 1 0 0 1 1 d[15:8] 1 0 1 0 2 d[23:16] 1 0 1 1 3 d[31:24] 1 1 0 0 4 d[39:32] 1 1 0 1 5 d[47:40] 1 1 1 0 6 d[53:48] 1 1 1 1 7 d[63:54] 76543210 adck bbck dfs masr ddir bl2 bo[9:8] 00000000
scsi registers 4-65 bbck clock byte counter 6 setting this bit decrements the byte count contained in the 24-bit dma byte counter (dbc) register. it is decremented based on the dbc contents and the current dma next address (dnad) value. this bit automatically clears itself after decrementing the dbc register. dfs dma fifo size 5 this bit controls the size of the dma fifo. when clear, the dma fifo appears as only 112 bytes deep. when set, the dma fifo size increases to 944 bytes. using an 112-byte fifo allows software written for other sym53c8xx family chips to properly calculate the number of bytes residing in the chip after a target disconnect. the default value of this bit is zero. masr master control for set or reset pulses 4 this bit controls the operation of bit 3. when this bit is set, bit 3 asserts the corresponding signals. when this bit is cleared, bit 3 deasserts the corresponding signals. do not change this bit and bit 3 in the same write cycle. ddir dma direction 3 setting this bit either asserts or deasserts the internal dma write (dmawr) direction signal depending on the current status of the masr bit in this register. asserting the dmawr signal indicates that data is transferred from the scsi bus to the host bus. deasserting the dmawr signal transfers data from the host bus to the scsi bus. bl2 burst length bit 2 2 this bit works with bits 6 and 7 (bl[1:0]) in the dma mode (dmode) , 0x38 register to determine the burst length. for complete de?nitions of this ?eld, refer to the descriptions of dmode bits 6 and 7. this bit is disabled if an 112-byte fifo is selected by clearing the dma fifo size bit. bo[9:8] dma fifo byte offset counter, bits [9:8] [1:0] these are the upper two bits of the dfboc. the dfboc consists of these bits and the dma fifo (dfifo) bits [7:0].
4-66 registers register: 0x23 chip test six (ctest6) read/write df[7:0] dma fifo [7:0] writing to this register writes data to the appropriate byte lane of the dma fifo as determined by the fbl bits in the chip test four (ctest4) register. reading this register unloads data from the appropriate byte lane of the dma fifo as determined by the fbl bits in the ctest4 register. data written to the fifo is loaded into the top of the fifo. data read out of the fifo is taken from the bottom. to prevent dma data from being corrupted, this register should not be accessed before starting or restarting scripts operation. write to this register only when testing the dma fifo using the chip test four (ctest4) register. writing to this register while the test mode is not enabled produces unexpected results. registers: 0x24C0x26 dma byte counter (dbc) read/write this 24-bit register determines the number of bytes transferred in a block move instruction. while sending data to the scsi bus, the counter is decremented as data is moved into the dma fifo from memory. while receiving data from the scsi bus, the counter is decremented as data is written to memory from the SYM53C896 scsi function. the dbc counter is decremented each time data is transferred on the pci bus. it is decremented by an amount equal to the number of bytes that are transferred. the maximum number of bytes that can be transferred in any one block move command is 16,777,215 bytes. the maximum value that can be loaded into the dma byte counter (dbc) register is 0xffffff. if the instruction is a block move and a value of 0x000000 is loaded into the 7 0 df[7:0] 00000000
scsi registers 4-67 dbc register, an illegal instruction interrupt occurs if the SYM53C896 scsi function is not in the target mode, command phase. the dma byte counter (dbc) register is also used to hold the least signi?cant 24 bits of the ?rst dword of a scripts fetch, and to hold the offset value during table indirect i/o scripts. for a complete description see chapter 5, scsi scripts instruction set . the power-up value of this register is indeterminate. register: 0x27 dma command (dcmd) read/write this 8-bit register determines the instruction for the SYM53C896 scsi function to execute. this register has a different format for each instruction. for a complete description see chapter 5, scsi scripts instruction set . registers: 0x28C0x2b dma next address (dnad) read/write this 32-bit register contains the general purpose address pointer. at the start of some scripts operations, its value is copied from the dma scripts pointer save (dsps) register. its value may not be valid except in certain abort conditions. the default value of this register is zero. registers: 0x2cC0x2f dma scripts pointer (dsp) read/write to execute scsi scripts, the address of the ?rst scripts instruction must be written to this register. in normal scripts operation, once the starting address of the scripts is written to this register, scripts are automatically fetched and executed until an interrupt condition occurs. in the single step mode, there is a single step interrupt after each instruction is executed. the dma scripts pointer (dsp) register does not need to be written with the next address, but the start dma bit (bit 2, dma control (dcntl) register) must be set each time the step interrupt occurs to fetch and execute the next scripts command. when
4-68 registers writing this register eight bits at a time, writing the upper eight bits begins execution of scsi scripts. the default value of this register is zero. registers: 0x30C0x33 dma scripts pointer save (dsps) read/write this register contains the second dword of a scripts instruction. it is overwritten each time a scripts instruction is fetched. when a scripts interrupt instruction is executed, this register holds the interrupt vector. the power-up value of this register is indeterminate. registers: 0x34C0x37 scratch register a (scratcha) read/write this is a general purpose, user-de?nable scratch pad register. apart from cpu access, only register read/write and memory moves into the scratch register alter its contents. the power-up value of this register is indeterminate. a special mode of this register is enabled by setting the pci con?guration info enable bit in the chip test two (ctest2) register. if this bit is set, the scratch register a (scratcha) register returns bits [31:10] of the pci base address register one (memory) in bits [31:10] of the scratch a register when read. bits [9:0] of scratch a will always return zero in this mode. writes to the scratcha register are unaffected. clearing the pci con?guration info enable bit causes the scratch a register to return to normal operation. register: 0x38 dma mode (dmode) read/write bl burst length [7:6] these bits control the maximum number of dwords transferred per bus ownership, regardless of whether the 76543210 bl siom diom erl ermp bof man 00000000
scsi registers 4-69 transfers are back to back, burst, or a combination of both. this value is also independent of the width (64 or 32 bits) of the data transfer on the pci bus. the SYM53C896 scsi function asserts the bus request (req/) output when the dma fifo can accommodate a transfer of at least one burst threshold of data. bus request (req/) is also asserted during start-of-transfer and end-of-transfer cleanup and alignment, even if less than a full burst of transfers is performed. the SYM53C896 scsi function inserts a fairness delay of four clks between burst transfers (as set in bl[2:0]) during normal operation. the fairness delay is not inserted during pci retry cycles. this gives the cpu and other bus master devices the opportunity to access the pci bus between bursts. the SYM53C896 will only support burst thresholds of up to 16 dwords in the small fifo mode. setting the burst threshold to higher than 16 dwords in the small fifo mode will yield unexpected results in burst lengths. the big fifo mode can be activated by setting bit 5 of the chip test five (ctest5) register. siom source i/o-memory enable 5 this bit is de?ned as an i/o memory enable bit for the source address of a memory move or block move command. if this bit is set, then the source address is in i/o space; and if cleared, then the source address is in memory space. bl2 (ctest5 bit 2) bl1 bl0 burst length transfers dwords 0002 4 0014 8 010816 0111632 1 1003264 1 1 0 1 64 128 1 1 1 0 64 128 1 1 1 1 reserved reserved 1. the 944 byte fifo must be enabled for these burst sizes.
4-70 registers this function is useful for register-to-memory operations using the memory move instruction when a SYM53C896 scsi function is i/o mapped. bits 4 and 5 of the chip test two (ctest2) register are used to determine the con?guration status of the SYM53C896 scsi function. diom destination i/o-memory enable 4 this bit is de?ned as an i/o memory enable bit for the destination address of a memory move or block move command. if this bit is set, then the destination address is in i/o space; and if cleared, then the destination address is in memory space. this function is useful for memory-to-register operations using the memory move instruction when a SYM53C896 scsi function is i/o mapped. bits 4 and 5 of the chip test two (ctest2) register are used to determine the con?guration status of the SYM53C896 scsi function. erl enable read line 3 this bit enables a pci read line command. if this bit is set and the chip is about to execute a read cycle other than an opcode fetch, then the command is 0b1110. ermp enable read multiple 2 if this bit is set and cache mode is enabled, a read multiple command is used on all read cycles when it is legal. bof burst opcode fetch enable 1 setting this bit causes the SYM53C896 scsi function to fetch instructions in burst mode. speci?cally, the chip bursts in the ?rst two dwords of all instructions using a single bus ownership. if the instruction is a memory-to- memory move type, the third dword is accessed in a subsequent bus ownership. if the instruction is an indirect type, the additional dword is accessed in a subsequent bus ownership. if the instruction is a table indirect block move type, the chip accesses the remaining two dwords in a subsequent bus ownership, thereby fetching the four dwords required in two bursts of two dwords each. if prefetch is enabled, this bit has no effect. this bit also has no effect on fetches out of scripts ram.
scsi registers 4-71 man manual start mode 0 setting this bit prevents the SYM53C896 scsi function from automatically fetching and executing scsi scripts when the dma scripts pointer (dsp) register is written. when this bit is set, the start dma bit in the dma control (dcntl) register must be set to begin scripts execution. clearing this bit causes the SYM53C896 scsi function to automatically begin fetching and executing scsi scripts when the dma scripts pointer (dsp) register is written. this bit normally is not used for scsi scripts operations. register: 0x39 dma interrupt enable (dien) read/write r reserved 7 mdpe master data parity error 6 bf bus fault 5 abrt aborted 4 ssi single step interrupt 3 sir scripts interrupt instruction received 2 r reserved 1 iid illegal instruction detected 0 this register contains the interrupt mask bits corresponding to the interrupting conditions described in the dma status (dstat) register. an interrupt is masked by clearing the appropriate mask bit. masking an interrupt prevents inta/ (for function a) or intb/ (for function b) from being asserted for the corresponding interrupt, but the status bit is still set in the dma status (dstat) register. masking an interrupt does not prevent setting the interrupt status zero (istat0) dip. all dma interrupts are considered fatal, therefore scripts stops running when this 76543210 r mdpe bf abrt ssi sir r iid x00000 x0
4-72 registers condition occurs, whether or not the interrupt is masked. setting a mask bit enables the assertion of inta/, or intb/, for the corresponding interrupt. (a masked nonfatal interrupt does not prevent unmasked or fatal interrupts from getting through; interrupt stacking begins when either the interrupt status zero (istat0) sip or dip bit is set.) the inta/ and intb/ outputs are latched. once asserted, they remain asserted until the interrupt is cleared by reading the appropriate status register. masking an interrupt after the inta/, or intb/, output is asserted does not cause deassertion of inta/, or intb/. for more information on interrupts, see chapter 2, functional description . register: 0x3a scratch byte register (sbr) read/write this is a general purpose register. apart from cpu access, only register read/write and memory moves into this register alter its contents. the default value of this register is zero. this register is called the dma watchdog timer on previous sym53c8xx family products. register: 0x3b dma control (dcntl) read/write clse cache line size enable 7 setting this bit enables the SYM53C896 scsi function to sense and react to cache line boundaries set up by the dma mode (dmode) or pci cache line size register, whichever contains the smaller value. clearing this bit disables the cache line size logic and the SYM53C896 scsi function monitors the cache line size using the dmode register. 76543210 clse pff pfen ssm irqm std irqd com 00000000
scsi registers 4-73 pff prefetch flush 6 setting this bit causes the prefetch unit to ?ush its contents. this bit clears after the ?ush is complete. pfen prefetch enable 5 setting this bit enables an 8-dword scripts instruction prefetch unit. the prefetch unit, when enabled, will fetch 8 dwords of instructions and instruction operands in bursts of 4 or 8 dwords. prefetching instructions allows the SYM53C896 scsi function to make more ef?cient use of the system pci bus, thus improving overall system performance. the unit will ?ush whenever the pff bit is set, as well as on all transfer control instructions when the transfer conditions are met, on every write to the dma scripts pointer (dsp) , on every regular mmov instruction, and when any interrupt is generated. the unit automatically determines the maximum burst size that it is capable of performing based on the burst length as determined by the values in the dma mode (dmode) register. if the burst threshold is set to 8 dwords the prefetch unit will fetch instructions in two bursts of 4 dwords. if the burst threshold is set to 16 dwords or greater the prefetch unit will fetch instructions in one burst of 8 dwords. burst thresholds of less than 8 dwords will cause the prefetch unit to be disabled. pci cache commands (read line and read multiple) will be issued appropriately if pci caching is enabled. prefetching from scripts ram is not supported and is unnecessary due to the speed of the fetches. when fetching from scripts ram the setting of this bit will have no effect on the fetch mechanism from scripts ram. the prefetch unit does not support 64-bit data instruction fetches across the pci bus. prefetches of scripts instructions will always be 32 bits in width. ssm single step mode 4 setting this bit causes the SYM53C896 scsi function to stop after executing each scripts instruction, and generate a single step interrupt. when this bit is cleared the SYM53C896 scsi function does not stop after each instruction. it continues fetching and executing instructions until an interrupt condition occurs. for normal scsi scripts operation, keep this bit cleared. to restart the SYM53C896 scsi function after it generates
4-74 registers a scripts step interrupt, read the interrupt status zero (istat0) and dma status (dstat) registers to recognize and clear the interrupt. then set the start dma bit in this register. irqm irq mode 3 when set, this bit enables a totem pole driver for the inta/, or intb/ pin. when cleared, this bit enables an open drain driver for the inta/, or intb/, pin with an internal weak pull-up. the bit should remain cleared to retain full pci compliance. std start dma operation 2 the SYM53C896 scsi function fetches a scsi scripts instruction from the address contained in the dma scripts pointer (dsp) register when this bit is set. this bit is required if the SYM53C896 scsi function is in one of the following modes: manual start mode C bit 0 in the dma mode (dmode) register is set single step mode C bit 4 in the dma control (dcntl) register is set when the SYM53C896 scsi function is executing scripts in manual start mode, the start dma bit must be set to start instruction fetches, but need not be set again until an interrupt occurs. when the SYM53C896 scsi function is in single step mode, set the start dma bit to restart execution of scripts after a single step interrupt. irqd inta, intb disable 1 setting this bit disables the inta (for scsi function a), or intb (for scsi function b) pin. clearing the bit enables normal operation. as with any other register other than interrupt status zero (istat0) , interrupt status one (istat1) , mailbox zero (mbox0) , mailbox one (mbox1), this register cannot be accessed except by a scripts instruction during scripts execution. for more information on the use of this bit in interrupt handling, see chapter 2, functional description . com sym53c700 compatibility 0 when the com bit is cleared, the SYM53C896 scsi function behaves in a manner compatible with the
scsi registers 4-75 sym53c700; selection/reselection ids are stored in both the scsi selector id (ssid) and scsi first byte received (sfbr) registers. this bit is not affected by a software reset. if the com bit is cleared, do not access this register using scripts operation as nondeterminate operations may occur. (this includes scripts read/write operations and conditional transfer control instructions that initialize the scsi first byte received (sfbr) register.) when the com bit is set, the id is stored only in the scsi selector id (ssid) register, protecting the scsi first byte received (sfbr) from being overwritten if a selection/reselection occurs during a dma register-to- register operation. registers: 0x3cC0x3f adder sum output (adder) read only this register contains the output of the internal adder, and is used primarily for test purposes. the power-up value for this register is indeterminate. register: 0x40 scsi interrupt enable zero (sien0) read/write this register contains the interrupt mask bits corresponding to the interrupting conditions described in the scsi interrupt status zero (sist0) register. an interrupt is masked by clearing the appropriate mask bit. for more information on interrupts see chapter 2, functional description . m/a scsi phase mismatch - initiator mode; scsi atn condition - target mode 7 in the initiator mode, this bit is set when the scsi phase asserted by the target and sampled during sreq/ does not match the expected phase in the scsi output control 76543210 m/a cmp sel rsl sge udc rst par 00000000
4-76 registers latch (socl) register. this expected phase is automatically written by scsi scripts. in the target mode, this bit is set when the initiator asserts satn/. see the disable halt on parity error or satn/ condition bit in the scsi control one (scntl1) register for more information on when this status is actually raised. cmp function complete 6 indicates full arbitration and selection sequence is completed. sel selected 5 indicates the SYM53C896 scsi function is selected by a scsi initiator device. set the enable response to selection bit in the scsi chip id (scid) register for this to occur. rsl reselected 4 indicates the SYM53C896 scsi function is reselected by a scsi target device. set the enable response to reselection bit in the scsi chip id (scid) register for this to occur. sge scsi gross error 3 the following conditions are considered scsi gross errors: data under?ow - reading the scsi fifo when no data is present. data over?ow - writing to the scsi fifo while it is full. offset under?ow - receiving a sack/ pulse in the target mode before the corresponding sreq/ is sent. offset over?ow - receiving a sreq/ pulse in the initiator mode, and exceeding the maximum offset (de?ned by the mo[3:0] bits in the scsi transfer (sxfer) register). a phase change in the initiator mode, with an outstanding sreq/sack offset. residual data in scsi fifo - starting a transfer other than synchronous data receive with data left in the scsi synchronous receive fifo.
scsi registers 4-77 udc unexpected disconnect 2 this condition only occurs in the initiator mode. it happens when the target to which the SYM53C896 scsi function is connected disconnects from the scsi bus unexpectedly. see the scsi disconnect unexpected bit in the scsi control two (scntl2) register for more information on expected versus unexpected disconnects. any disconnect in the low level mode causes this condition. rst scsi reset condition 1 indicates assertion of the srst/ signal by the SYM53C896 scsi function or any other scsi device. this condition is edge-triggered, so multiple interrupts cannot occur because of a single srst/ pulse. par scsi parity error 0 indicates detection by the SYM53C896 scsi function of a parity error while receiving or sending scsi data. see the disable halt on parity error or satn/ condition bits in the scsi control one (scntl1) register for more infor- mation on when this condition is actually raised. register: 0x41 scsi interrupt enable one (sien1) read/write this register contains the interrupt mask bits corresponding to the interrupting conditions described in the scsi interrupt status one (sist1) register. an interrupt is masked by clearing the appropriate mask bit. for more information on interrupts refer to chapter 2, functional description . r reserved [7:5] sbmc scsi bus mode change 4 setting this bit allows the SYM53C896 to generate an interrupt when the diffsens pin detects a change in voltage level that indicates the scsi bus has changed between se, lvd, or hvd modes. for example, when this bit is cleared and the scsi bus changes modes, irq/ 7 543210 r sbmc r sto gen hth x x xx x000
4-78 registers does not assert and the sip bit in the interrupt status zero (istat0) register is not set. however, bit 4 in the scsi interrupt status one (sist1) register is set. setting this bit allows the interrupt to occur. r reserved 3 sto selection or reselection time-out 2 the scsi device which the SYM53C896 scsi function is attempting to select or reselect does not respond within the programmed time-out period. see the description of the scsi timer zero (stime0) register bits [3:0] for more information on the time-out timer. gen general purpose timer expired 1 the general purpose timer is expired. the time measured is the time between enabling and disabling of the timer. see the description of the scsi timer one (stime1) register, bits [3:0], for more information on the general purpose timer. hth handshake-to-handshake timer expired 0 the handshake-to-handshake timer is expired. the time measured is the scsi request-to-request (target) or acknowledge-to-acknowledge (initiator) period. see the description of the scsi timer zero (stime0) register, bits [7:4], for more information on the handshake-to-handshake timer.
scsi registers 4-79 register: 0x42 scsi interrupt status zero (sist0) read only reading the scsi interrupt status zero (sist0) register returns the status of the various interrupt conditions, whether they are enabled in the scsi interrupt enable zero (sien0) register or not. each bit set indicates occurrence of the corresponding condition. reading the sist0 clears the interrupt status. reading this register clears any bits that are set at the time the register is read, but does not necessarily clear the register because additional interrupts may be pending (the SYM53C896 scsi functions stack interrupts). scsi interrupt conditions are individually masked through the scsi interrupt enable zero (sien0) register. when performing consecutive 8-bit reads of the dma status (dstat) , scsi interrupt status zero (sist0) , and scsi interrupt status one (sist1) registers (in any order), insert a delay equivalent to 12 clock periods between the reads to ensure the interrupts clear properly. also, if reading the registers when both the interrupt status zero (istat0) sip and dip bits may not be set, read the sist0 and sist1 registers before the dstat register to avoid missing a scsi interrupt. for more information on interrupts refer to chapter 2, functional description . m/a initiator mode: phase mismatch; target mode: satn/ active 7 in the initiator mode, this bit is set if the scsi phase asserted by the target does not match the instruction. the phase is sampled when sreq/ is asserted by the target. in the target mode, this bit is set when the satn/ signal is asserted by the initiator. cmp function complete 6 this bit is set when an arbitration only or full arbitration sequence is completed. sel selected 5 this bit is set when the SYM53C896 scsi function is selected by another scsi device. the enable response 76543210 m/a cmp sel rsl sge udc rst par 00000000
4-80 registers to selection bit must be set in the scsi chip id (scid) register (and the response id zero (respid0) and response id one (respid1) registers must hold the chips id) for the SYM53C896 scsi function to respond to selection attempts. rsl reselected 4 this bit is set when the SYM53C896 scsi function is reselected by another scsi device. the enable response to reselection bit must be set in the scsi chip id (scid) register (and the response id zero (respid0) and response id one (respid1) registers must hold the chips id) for the SYM53C896 scsi function to respond to reselection attempts. sge scsi gross error 3 this bit is set when the SYM53C896 scsi function encounters a scsi gross error condition. the following conditions can result in a scsi gross error condition: data under?ow - reading the scsi fifo when no data is present. data over?ow - writing too many bytes to the scsi fifo, or the synchronous offset causes overwriting the scsi fifo. offset under?ow - the SYM53C896 scsi function is operating in the target mode and a sack/ pulse is received when the outstanding offset is zero. offset over?ow - the other scsi device sends a sreq/ or sack/ pulse with data which exceeds the maximum synchronous offset de?ned by the scsi transfer (sxfer) register. a phase change occurs with an outstanding synchronous offset when the SYM53C896 scsi function is operating as an initiator. residual data in the synchronous data fifo - a transfer other than synchronous data receive is started with data left in the synchronous data fifo. udc unexpected disconnect 2 this bit is set when the SYM53C896 scsi function is operating in the initiator mode and the target device unexpectedly disconnects from the scsi bus. this bit is
scsi registers 4-81 only valid when the SYM53C896 scsi function operates in the initiator mode. when the scsi function operates in the low level mode, any disconnect causes an interrupt, even a valid scsi disconnect. this bit is also set if a selection time-out occurs (it may occur before, at the same time, or stacked after the sto interrupt, since this is not considered an expected disconnect). rst scsi rst/ received 1 this bit is set when the SYM53C896 scsi function detects an active srst/ signal, whether the reset is generated external to the chip or caused by the assert srst/ bit in the scsi control one (scntl1) register. this scsi reset detection logic is edge-sensitive, so that multiple interrupts are not generated for a single assertion of the srst/ signal. par parity error 0 this bit is set when the SYM53C896 scsi function detects a parity error while receiving scsi data. the enable parity checking bit (bit 3 in the scsi control zero (scntl0) register) must be set for this bit to become active. the SYM53C896 scsi function always generates parity when sending scsi data. register: 0x43 scsi interrupt status one (sist1) read only reading the sist1 register returns the status of the various interrupt conditions, whether they are enabled in the scsi interrupt enable one (sien1) register or not. each bit that is set indicates an occurrence of the corresponding condition. reading the sist1 clears the interrupt condition. 7 543210 r sbmc r sto gen hth 0 0 00 0000
4-82 registers r reserved [7:5] sbmc scsi bit mode change 4 this bit is set when the diffsens pin detects a change in voltage level that indicates the scsi bus has switched between se, lvd or hvd modes. r reserved 3 sto selection or reselection time-out 2 the scsi device which the SYM53C896 scsi function is attempting to select or reselect does not respond within the programmed time-out period. see the description of the scsi timer zero (stime0) register, bits [3:0], for more information on the time-out timer. gen general purpose timer expired 1 this bit is set when the general purpose timer expires. the time measured is the time between enabling and disabling of the timer. see the description of the scsi timer one (stime1) register, bits [3:0], for more information on the general purpose timer. hth handshake-to-handshake timer expired 0 this bit is set when the handshake-to-handshake timer expires. the time measured is the scsi request to request (target) or acknowledge-to-acknowledge (initiator) period. see the description of the scsi timer zero (stime0) register, bits [7:4], for more information on the handshake-to-handshake timer. register: 0x44 scsi longitudinal parity (slpar) read/write this register performs a bytewise longitudinal parity check on all scsi data received or sent through the scsi core. if one of the bytes received or sent (usually the last) is the set of correct even parity bits, slpar should go to zero (assuming it started at zero). as an example, suppose that the following three data bytes and one check byte are received from the scsi bus (all signals are shown active high):
scsi registers 4-83 a one in any bit position of the ?nal slpar value would indicate a transmission error. the slpar register is also used to generate the check bytes for scsi send operations. if the scsi longitudinal parity (slpar) register contains all zeros prior to sending a block move, it contains the appropriate check byte at the end of the block move. this byte must then be sent across the scsi bus. note: writing any value to this register clears it to zero. the longitudinal parity checks are meant to provide an added measure of scsi data integrity and are entirely optional. this register does not latch scsi selection/reselection ids under any circumstances. the default value of this register is zero. the longitudinal parity function normally operates as a byte function. during 16-bit transfers, the high and low bytes are xored together and then xored into the current longitudinal parity value. by setting the slpmd bit in the scsi control two (scntl2) register, the longitudinal parity function is made to operate as a word-wide function. during 16-bit transfers, the high byte of the scsi bus is xored with the high byte of the current longitudinal parity value, and the low byte of the scsi bus is xored with the low byte of the current longitudinal parity value. in this mode, the 16-bit longitudinal parity value is accessed a byte at a time through the scsi longitudinal parity (slpar) register. which byte is accessed is controlled by the slphben bit in the scsi control two (scntl2) register. data bytes running slpar C 00000000 1. 11001100 11001100 (xor of word 1) 2. 01010101 10011001 (xor of word 1 and 2) 3. 00001111 10010110 (xor of word 1, 2 and 3) 4. 10010110 00000000
4-84 registers register: 0x45 scsi wide residue (swide) read/write after a wide scsi data receive operation, this register contains a residual data byte if the last byte received was never sent across the dma bus. it represents either the ?rst data byte of a subsequent data transfer, or it is a residue byte which should be cleared when an ignore wide residue message is received. it may also be an overrun data byte. the power-up value of this register is indeterminate. register: 0x46 chip type (ctype) read only typ chip type [7:4] these bits identify the chip type for software purposes. note: these bits no longer identify an 8xx device. these bits have been set to 0xf to indicate that the device should be uniquely identi?ed by setting the pci con?guration enable bit in the chip test two (ctest2) register and using the pci revision id (rev id) and pci device id which will be shadowed in the scripts fetch selector (sfs) register. any devices that contain the value 0xf in this register should use this mechanism to uniquely identify the device. r reserved [3:0] 7430 typ r 1111 x x x x
scsi registers 4-85 register: 0x47 general purpose pin control (gpcntl) read/write this register is used to determine if the pins controlled by the general purpose (gpreg) are inputs or outputs. bits [4:0] in gpcntl correspond to bits [4:0] in the gpreg register. when the bits are enabled as inputs, an internal pull-down is also enabled. if either scsi function gpcntl register has a gpio pin set as an output, the pin is enabled as an output. if both the scsi function gpreg registers de?ne a single gpio pin as an output, the results are indeterminate. me master enable 7 the internal bus master signal is presented on gpio1 if this bit is set, regardless of the state of bit 1 (gpio1). fe fetch enable 6 the internal opcode fetch signal is presented on gpio0 if this bit is set, regardless of the state of bit 0 (gpio0). ledc led_cntl 5 the internal connected signal (bit 3 of the interrupt status zero (istat0) register) will be presented on gpio0 if this bit is set and bit 6 of gpcntl is cleared and the chip is not in progress of performing an eeprom autodownload regardless of the state of bit 0 (gpio0). this provides a hardware solution to driving a scsi activity led in many implementations of lsi logic scsi chips. gpio gpio enable [4:2] general purpose control, corresponding to bit 4 in the general purpose (gpreg) register and the gpio4 pin. gpio4 powers up as a general purpose output, and gpio[3:2] power-up as general purpose inputs. gpio gpio enable [1:0] these bits power-up set, causing the gpio1 and gpio0 pins to become inputs. clearing these bits causes gpio[1:0] to become outputs. 7654 210 me fe ledc gpio gpio 00001111
4-86 registers register: 0x48 scsi timer zero (stime0) read/write hth[3:0] handshake-to-handshake timer period [7:4] these bits select the handshake-to-handshake time-out period, the maximum time between scsi handshakes (sreq/ to sreq/ in target mode, or sack/ to sack/ in the initiator mode). when this timing is exceeded, an interrupt is generated and the hth bit in the scsi interrupt status one (sist1) register is set. the following table contains time-out periods for the handshake-to- handshake timer, the selection/reselection timer (bits [3:0]), and the general purpose timer ( scsi timer one (stime1) bits [3:0]). for a more detailed explanation of interrupts, refer to chapter 2, functional description . 743 0 hth[3:0] sel[3:0] 00000000
scsi registers 4-87 sel[3:0] selection time-out [3:0] these bits select the scsi selection/reselection time-out period. when this timing (plus the 200 m s selection abort time) is exceeded, the sto bit in the scsi interrupt status one (sist1) register is set. for a more detailed explanation of interrupts, refer to chapter 2, functional description . hth[7:4], sel[3:0], gen[3:0] 1 minimum time-out (40 or 160 mhz) 2 0000 disabled 0001 125 m s 0010 250 m s 0011 500 m s 0100 1 ms 0101 2 ms 0110 4 ms 0111 8 ms 1000 16 ms 1001 32 ms 1010 64 ms 1011 128 ms 1100 256 ms 1101 512 ms 1110 1.024 sec 1111 2.048 sec 1. these values will be correct if the ccf bits in the scsi control three (scntl3) register are set according to the valid combinations in the bit description. 2. a quadrupled 40 mhz clock is required for ultra2 scsi operation.
4-88 registers register: 0x49 scsi timer one (stime1) read/write r reserved 7 hthba handshake-to-handshake timer bus activity enable 6 setting this bit causes this timer to begin testing for scsi req/ and ack/ activity as soon as sbsy/ is asserted, regardless of the agents participating in the transfer. gensf general purpose timer scale factor 5 setting this bit causes this timer to shift by a factor of 16. refer to the scsi timer zero (stime0) register description for details. 76543 0 r hthba gensf hthsf gen[3:0] x0000000
scsi registers 4-89 hthsf handshake-to-handshake timer scale factor 4 setting this bit causes this timer to shift by a factor of 16. refer to the scsi timer zero (stime0) register description for details. gen[3:0] general purpose timer period [3:0] these bits select the period of the general purpose timer. the time measured is the time between enabling and disabling of the timer. when this timing is exceeded, the gen bit in the scsi interrupt status one (sist1) register is set. refer to the table under scsi timer zero (stime0) , bits [3:0], for the available time-out periods. hth[7:4], sel[3:0], gen[3:0] 1 minimum time-out (50 mhz clock) 2 hthsf = 0, gensf = 0 hthsf = 1, gensf = 1 0000 disabled disabled 0001 100 m s 1.6 ms 0010 200 m s 3.2 ms 0011 400 m s 6.4 ms 0100 800 m s 12.8 ms 0101 1.6 ms 25.6 ms 0110 3.2 ms 51.2 ms 0111 6.4 ms 102.4 ms 1000 12.8 ms 204.8 ms 1001 25.6 ms 409.6 ms 1010 51.2 ms 819.2 ms 1011 102.4 ms 1.6 s 1100 204.8 ms 3.2 s 1101 409.6 ms 6.4 s 1110 819.2 ms 12.8 s 1111 1.6 s 25.6 s 1. these values will be correct if the ccf bits in the scsi control three (scntl3) register are set according to the valid combinations in the bit description. 2. 50 mhz clock is not supported for ultra2 scsi operation.
4-90 registers note: to reset a timer before it expires and obtain repeatable delays, the time value must be written to zero ?rst, and then written back to the desired value. this is also required when changing from one time value to another. hth[7:4], sel[3:0], gen[3:0] 1 minimum time-out (40 or 160 mhz clock) 2 hthsf = 0, gensf = 0 hthsf = 1, gensf = 1 0000 disabled disabled 0001 125 m s2ms 0010 250 m s4ms 0011 500 m s8ms 0100 1 m s16ms 0101 2 ms 32 ms 0110 4 ms 64 ms 0111 8 ms 128 ms 1000 16 ms 256 ms 1001 32 ms 512 ms 1010 64 ms 1 s 1011 128 ms 2 s 1100 256 ms 4.1 s 1101 512 ms 8.2 s 1110 1.024 s 16.4 s 1111 2.048 s 32.8 s 1. these values will be correct if the ccf bits in the scsi control three (scntl3) register are set according to the valid combinations in the bit description. 2. ultra2 scsi operation requires a quadrupled 40 mhz clock.
scsi registers 4-91 register: 0x4a response id zero (respid0) read/write respid0 and response id one (respid1) contain the selection or reselection ids. in other words, these two 8-bit registers contain the id that the chip responds to on the scsi bus. each bit represents one possible id with the most signi?cant bit of response id one (respid1) representing id 15 and the least signi?cant bit of respid0 representing id 0. the scsi chip id (scid) register still contains the chip id used during arbitration. the chip can respond to more than one id because more than one bit can be set in the respid1 and respid0 registers. however, the chip can arbitrate with only one id value in the scsi chip id (scid) register. register: 0x4b response id one (respid1) read/write response id zero (respid0) and respid1 contain the selection or reselection ids. in other words, these two 8-bit registers contain the id that the chip responds to on the scsi bus. each bit represents one possible id with the most signi?cant bit of respid1 representing id 15 and the least signi?cant bit of respid0 representing id 0. the scsi chip id (scid) register still contains the chip id used during arbitration. the chip can respond to more than one id because more than one bit can be set in the respid1 and respid0 registers. however, the chip can arbitrate with only one id value in the scsi chip id (scid) register. 7 0 id xxxxxxxx 15 8 id xxxxxxxx
4-92 registers register: 0x4c scsi test zero (stest0) read only ssaid scsi selected as id [7:4] these bits contain the encoded value of the scsi id that the SYM53C896 scsi function is selected or reselected as during a scsi selection or reselection phase. these bits are read only and contain the encoded value of 0C15 possible ids that could be used to select the SYM53C896 scsi function. during a scsi selection or reselection phase when a valid id is put on the bus, and the SYM53C896 scsi function responds to that id, the selected as id is written into these bits. these bits are used with response id zero (respid0) and response id one (respid1) registers to allow response to multiple ids on the bus. slt selection response logic test 3 this bit is set when the SYM53C896 scsi function is ready to be selected or reselected. this does not take into account the bus settle delay of 400 ns. this bit is used for functional test and fault purposes. art arbitration priority encoder test 2 this bit is always set when the SYM53C896 scsi function exhibits the highest priority id asserted on the scsi bus during arbitration. it is primarily used for chip level testing, but it may be used during low level mode operation to determine if the SYM53C896 scsi function won arbitration. soz scsi synchronous offset zero 1 this bit indicates that the current synchronous sreq/, sack/ offset is zero. this bit is not latched and may change at any time. it is used in low level synchronous scsi operations. when this bit is set, the SYM53C896 scsi functioning as an initiator, is waiting for the target to request data transfers. if the SYM53C896 scsi is 7 43210 ssaid slt art soz som xxxx0011
scsi registers 4-93 functioning as a target, then the initiator has sent the offset number of acknowledges. som scsi synchronous offset maximum 0 this bit indicates that the current synchronous sreq/, sack/ offset is the maximum speci?ed by bits [3:0] in the scsi transfer (sxfer) register. this bit is not latched and may change at any time. it is used in low level synchronous scsi operations. when this bit is set, the SYM53C896 scsi is functioning as a target, and is waiting for the initiator to acknowledge the data transfers. if the SYM53C896 scsi is functioning as an initiator, then the target has sent the offset number of requests. register: 0x4d scsi test one (stest1) read/write sclk scsi clock 7 when set, this bit disables the external sclk (scsi clock) pin, and the chip uses the pci clock as the internal scsi clock. if a transfer rate of 10 mbytes/s (or 20 mbytes/s on a wide scsi bus) is desired on the scsi bus, this bit must be cleared and at least a 40 mhz external sclk must be provided. iso scsi isolation mode 6 this bit allows the SYM53C896 scsi function to put the scsi bidirectional and input pins into a low power mode when the scsi bus is not in use. when this bit is set, the scsi bus inputs are logically isolated from the scsi bus. r reserved [5:4] qen sclk quadrupler enable 3 this bit, when set, powers up the internal clock quadrupler circuit, which quadruples the sclk 40 mhz clock to an internal 160 mhz scsi clock required for fast-20 and fast-40 scsi operation. when cleared, this bit powers down the internal quadrupler circuit. 76543210 sclk iso r qen qsel irm[1:0] 00 x x0000
4-94 registers qsel sclk quadrupler select 2 this bit, when set, selects the output of the internal clock doubler for use as the internal scsi clock. when cleared, this bit selects the clock presented on sclk for use as the internal scsi clock. irm[1:0] interrupt routing mode [1:0] the SYM53C896 supports four different interrupt routing modes. these modes are described in the following table. each scsi core within the chip can be con?gured independently. mode 0 is the default mode and is compatible with ami raid upgrade products. register: 0x4e scsi test two (stest2) read/write sce scsi control enable 7 setting this bit allows assertion of all scsi control and data lines through the scsi output control latch (socl) and scsi output data latch (sodl) registers regardless of whether the SYM53C896 scsi function is con?gured as a target or initiator. mode bits [1:0] operation 0 00 if the int_dir/ input pin is low, interrupts are signaled on alt_intx/. otherwise, interrupts are signaled on both intx/ and alt_intx/. 1 01 interrupts are only signaled on intx/, not alt_intx/, and the int_dir/ input pin is ignored. 2 10 interrupts are only signaled on alt_intx/, and the int_dir/ input pin is ignored. 3 11 interrupts are signaled on both intx/ and alt_intx/, and the int_dir input pin is ignored. 76543210 sce rof dif slb szm aws ext low 00000000
scsi registers 4-95 note: do not set this bit during normal operation, since it could cause contention on the scsi bus. it is included for diagnostic purposes only. rof reset scsi offset 6 setting this bit clears any outstanding synchronous sreq/sack offset. if a scsi gross error occurs, set this bit. this bit automatically clears itself after resetting the synchronous offset. dif hvd or se/lvd 5 setting this bit allows the SYM53C896 scsi function to interface to external hvd transceivers. clearing this bit enables se or lvd operation. set this bit in the initialization routine if the hvd pair interface is used. slb scsi loopback mode 4 setting this bit allows the SYM53C896 scsi function to perform scsi loopback diagnostics. that is, it enables the scsi core to simultaneously perform as both the initiator and the target. szm scsi high impedance mode 3 setting this bit places all the open drain 48 ma scsi drivers into a high impedance state. this is to allow internal loopback mode operation without affecting the scsi bus. aws always wide scsi 2 when this bit is set, all scsi information transfers are done in the 16-bit wide mode. this includes data, message, command, status and reserved phases. normally, deassert this bit since 16-bit wide message, command, and status phases are not supported by the scsi speci?cations. ext extend sreq/sack/ filtering 1 lsi logic tolerant scsi receiver technology includes a special digital ?lter on the sreq/ and sack/ pins which causes the disregarding of glitches on deasserting edges. setting this bit increases the ?ltering period from 30 ns to 60 ns on the deasserting edge of the sreq/ and sack/ signals.
4-96 registers note: never set this bit during fast scsi (greater than 5 mbytes transfers per second) operations, because a valid assertion could be treated as a glitch. low scsi low level mode 0 setting this bit places the SYM53C896 scsi function in low level mode. in this mode, no dma operations occur, and no scripts execute. arbitration and selection may be performed by setting the start sequence bit as described in the scsi control zero (scntl0) register. scsi bus transfers are performed by manually asserting and polling scsi signals. clearing this bit allows instructions to be executed in the scsi scripts mode. note: it is not necessary to set this bit for access to the scsi bit-level registers ( scsi output data latch (sodl) , scsi bus control lines (sbcl) , and input registers). register: 0x4f scsi test three (stest3) read/write te tolerant enable 7 setting this bit enables the active negation portion of lsi logic tolerant technology. active negation causes the scsi request, acknowledge, data, and parity signals to be actively deasserted, instead of relying on external pull-ups, when the SYM53C896 scsi function is driving these signals. active deassertion of these signals occurs only when the SYM53C896 scsi function is in an information transfer phase. when operating in a differential environment or at fast scsi timings, tolerant active negation should be enabled to improve setup and deassertion times. active negation is disabled after reset or when this bit is cleared. for more information on lsi logic tolerant technology, see chapter 1, introduction . 76543210 te str hsc dsi s16 ttm csf stw 00000000
scsi registers 4-97 note: set this bit if the enable ultra scsi bit in scsi control three (scntl3) is set. str scsi fifo test read 6 setting this bit places the scsi core into a test mode in which the scsi fifo is easily read. reading the least signi?cant byte of the scsi output data latch (sodl) register causes the fifo to unload. the functions are summarized in the following table. hsc halt scsi clock 5 asserting this bit causes the internal divided scsi clock to come to a stop in a glitchless manner. this bit is used for test purposes or to lower i dd during a power-down mode. dsi disable single initiator response 4 if this bit is set, the SYM53C896 scsi function ignores all bus-initiated selection attempts that employ the single initiator option from scsi-1. in order to select the SYM53C896 scsi function while this bit is set, the SYM53C896 scsi functions scsi id and the initiators scsi id must both be asserted. assert this bit in scsi-2 systems so that a single bit error on the scsi bus is not interpreted as a single initiator response. s16 16-bit system 3 if this bit is set, all devices in the scsi system implementation are assumed to be 16-bit. this causes the SYM53C896 to always check the parity bit for scsi ids 15C8 during bus-initiated selection or reselection, assuming parity checking has been enabled. if an 8-bit scsi device attempts to select the SYM53C896 while this bit is set, the SYM53C896 will ignore the selection attempt. this is because the parity bit for ids 15C8 will not be driven. see the description of the enable parity checking bit in the scsi control zero (scntl0) register for more information. register name register operation fifo bits fifo function sodl read [15:0] unload sodl0 read [7:0] unload sodl1 read [15:8] none
4-98 registers ttm timer test mode 2 asserting this bit facilitates testing of the selection time-out, general purpose, and handshake-to-handshake timers by greatly reducing all three time-out periods. setting this bit starts all three timers and if the respective bits in the scsi interrupt enable one (sien1) register are asserted, the SYM53C896 scsi function generates interrupts at time-out. this bit is intended for internal manufacturing diagnosis and should not be used. csf clear scsi fifo 1 setting this bit causes the full ?ags for the scsi fifo to be cleared. this empties the fifo. this bit is self-clearing. in addition to the scsi fifo pointers, the sidl, sodl, and sodr full bits in the scsi status zero (sstat0) and scsi status two (sstat2) are cleared. stw scsi fifo test write 0 setting this bit places the scsi core into a test mode in which the fifo is easily read or written. while this bit is set, writes to the least signi?cant byte of the scsi output data latch (sodl) register cause the entire word contained in sodl to be loaded into the fifo. these functions are summarized in the following table. registers: 0x50C0x51 scsi input data latch (sidl) read only this register is used primarily for diagnostic testing, programmed i/o operation, or error recovery. data received from the scsi bus can be read from this register. data can be written to the scsi output data latch (sodl) register and then read back into the SYM53C896 by reading this register to allow loopback testing. when receiving scsi data, the data ?ows into this register and out to the host fifo. this register differs from the scsi bus data lines (sbdl) register; scsi input data latch (sidl) contains latched data and the scsi bus data lines (sbdl) always register name register operation fifo bits fifo function sodl write [15:0] load sodl0 write [7:0] load sodl1 write [15:8] none
scsi registers 4-99 contains exactly what is currently on the scsi data bus. reading this register causes the scsi parity bit to be checked, and causes a parity error interrupt if the data is not valid. the power-up values are indeterminate. register: 0x52 scsi test four (stest4) read only smode[1:0] scsi mode [7:6] these bits contain the encoded value of the scsi operating mode that is indicated by the voltage level sensed at the diffsens pin. the incoming scsi signal goes to a pair of analog comparators that determine the voltage window of the diffsens signal. these voltage windows indicate lvd, se, or hvd operation. the bit values are de?ned in the following table. lock frequency lock 5 this bit is used when enabling the scsi clock quadrupler, which allows the SYM53C896 to transfer data at ultra2 scsi rates. poll this bit for a 1 to determine that the clock quadrupler has locked to 160 mhz. for more information on enabling the clock quadrupler, refer to the descriptions of scsi test one (stest1) , bits 2 and 3. r reserved [4:0] 7654 0 smode[1:0] lock r 000 0 0 0 0 0 bits [7:6] operating mode 00 not possible 01 hvd or powered down (for hvd mode, the dif bit must also be set) 10 se 11 lvd scsi
4-100 registers register: 0x53 reserved registers: 0x54C0x55 scsi output data latch (sodl) read/write this register is used primarily for diagnostic testing or programmed i/o operation. data written to this register is asserted onto the scsi data bus by setting the assert data bus bit in the scsi control one (scntl1) register. this register is used to send data using programmed i/o. data ?ows through this register when sending data in any mode. it is also used to write to the synchronous data fifo when testing the chip. the power-up value of this register is indeterminate. register: 0x56 chip control 0 (ccntl0) read/write enpmj enable phase mismatch jump 7 upon setting this bit, any phase mismatches do not interrupt but force a jump to an alternate location to handle the phase mismatch. prior to actually taking the jump, the appropriate remaining byte counts and addresses will be calculated such that they can be easily stored to the appropriate memory location with the scripts store instruction. in the case of a scsi send, any data in the part will be automatically cleared after being accounted for. in the case of a scsi receive, all data will be ?ushed out of the part and accounted for prior to taking the jump. this feature does not cover, however, the byte that may appear in scsi wide residue (swide) . this byte must be ?ushed manually. this bit also enables the ?ushing mechanism to ?ush data during a data in phase mismatch in a more ef?cient manner. 76543210 enpmj pmjctl enndj disfc r dils dpr 0000 x x00
scsi registers 4-101 pmjctl jump control 6 this bit controls which decision mechanism is used when jumping on phase mismatch. when this bit is cleared the SYM53C896 will use jump address one phase mismatch jump address 1 (pmjad1) when the wsr bit is cleared and jump address two phase mismatch jump address 2 (pmjad2) when the wsr bit is set. when this bit is set the SYM53C896 will use jump address one (pmjad1) on data out (data out, command, message out) transfers and jump address two (pmjad2) on data in (data in, status, message in) transfers. note that the phase referred to here is the phase encoded in the block move scripts instruction, not the phase on the scsi bus that caused the phase mismatch. enndj enable jump on nondata phase mismatches 5 this bit controls whether or not a jump is taken during a nondata phase mismatch (i.e. message in, message out, status, or command). when this bit is cleared, jumps will only be taken on data in or data out phases and a phase mismatch interrupt will be generated for all other phases. when this bit is set, jumps will be taken regardless of the phase in the block move. note that the phase referred to here is the phase encoded in the block move scripts instruction, not the phase on the scsi bus that caused the phase mismatch. disfc disable auto fifo clear 4 this bit controls whether or not the fifo is automatically cleared during a data out phase mismatch. when set, data in the dma fifo as well as data in the scsi output data latch (sodl) and sodr (a hidden buffer register which is not accessible) registers will not be cleared after calculations on them are complete. when cleared, the dma fifo, sodl and sodr will automatically be cleared. this bit also disables the enhanced ?ushing mechanism. r reserved [3:2] dils disable internal load/store 1 this bit controls whether or not load/store data transfers, in which the source/destination is located in scripts ram, generate external pci cycles.
4-102 registers if cleared, load/store data transfers of this type will not generate pci cycles, but will stay internal to the chip. if set, load/store data transfers of this type will generate pci cycles. dpr disable pipe req 0 this bit controls whether or not overlapped arbitration on the pci bit is performed by asserting pci req/ for one scsi function while the other scsi function is executing a pci cycle. if set, overlapped arbitration will be disabled, and pci req/ will not be asserted during a pci master cycle being executed by this chip. register: 0x57 chip control 1 (ccntl1) read/write zmod high impedance mode 7 setting this bit causes the SYM53C896 scsi function to place all output and bidirectional pins except moe/_testout, into a high impedance state. when this bit is set, the moe/_testout pin becomes the output pin for the connectivity test of the SYM53C896 signals in the and-tree test mode. in order to read data out of the SYM53C896 scsi function, this bit must be cleared. this bit is intended for board-level testing only. do not set this bit during normal system operation. note: both scsi functions need to set this bit for the high impedance mode. r reserved [6:4] ddac disable dual address cycle (ddac) 3 when this bit is set, all 64-bit addressing as a master will be disabled. no dacs will be generated by the SYM53C896. 76 43 2 1 0 zmod r ddac 64timod en64tibmv en64dbmv 0 0 0 0x x 0 0
scsi registers 4-103 when this bit is cleared, the SYM53C896 will generate dacs based on the master operation being performed and the value of its associated selector register. 64timod 64-bit table indirect indexing mode 2 when this bit is cleared, bits [24:28] of the ?rst table entry dword will select one of 22 possible selectors to be used in a bmov operation. when this bit is set, bits [24:31] of the ?rst table entry dword will be copied directly into dma next address 64 (dnad64) to provide 40-bit addressing capability. this bit will only function if the en64tibmv bit is set. index mode 0 (64timod clear) table entry format: index mode 1 (64timod set) table entry format: en64tibmv enable 64-bit table indirect bmov 1 setting this bit enables 64-bit addressing for table indirect bmovs using the upper byte (bits [24:31]) of the ?rst dword of the table entry. when this bit is cleared table indirect bmovs will use the static block move selec- tor (sbms) register to obtain the upper 32 bits of the data address. en64dbmv enable 64-bit direct bmov 0 setting this bit enables the 64-bit version of a direct bmov. when this bit is cleared direct bmovs will use the static block move selector (sbms) register to obtain the upper 32 bits of the data address. bits [31:29] bits [28:24] bits [23:0] reserved sel index byte count source/destination address bits [31:24] bits [23:0] src/dest addr [39:32] byte count source/destination address [31:0]
4-104 registers registers: 0x58C0x59 scsi bus data lines (sbdl) read only this register contains the scsi data bus status. even though the scsi data bus is active low, these bits are active high. the signal status is not latched and is a true representation of exactly what is on the data bus at the time the register is read. this register is used when receiving data using programmed i/o. this register can also be used for diagnostic testing or in the low level mode. the power-up value of this register is indeterminate. if the chip is in the wide mode ( scsi control three (scntl3) , bit 3 and scsi test two (stest2) , bit 2 are set) and scsi bus data lines (sbdl) is read, both byte lanes are checked for parity regardless of phase. when in a nondata phase, this will cause a parity error interrupt to be generated because upper byte lane parity is invalid. registers: 0x5aC0x5b reserved registers: 0x5cC0x5f scratch register b (scratchb) read/write this is a general purpose user de?nable scratch pad register. apart from cpu access, only register read/write and memory moves directed at the scratch register will alter its contents. the power-up values are indeterminate. a special mode of this register can be enabled by setting the pci con?guration info enable bit in the chip test two (ctest2) register. if this bit is set, the scratch register b (scratchb) returns bits [31:13] of the scripts ram pci base address register two (scripts ram) in bits [31:13] of the scratch b register when read. when read, bits [12:0] of scratch b will always return zeros in this mode. writes to the scratch b register are unaffected. resetting the pci con?guration info enable bit causes the scratch b register to return to normal operation.
scsi registers 4-105 registers: 0x60C0x9f scratch registers cCr (scratchcCscratchr) read/write these are general purpose user de?nable scratch pad registers. apart from cpu access, only register read/write, memory moves and load/stores directed at a scratch register will alter its contents. the power-up values are indeterminate.
4-106 registers 4.3 64-bit scripts selectors the following registers are used to hold the upper 32-bit addresses for various scripts operations. when a particular type of scripts operation is performed, one of the 6 selector registers below will be used to generate a 64-bit address. if the selector for a particular device operation is zero, then a standard 32-bit address cycle will be generated. if the selector value is nonzero, then a dac will be issued with the entire 64-bit address. all selectors default to 0 (zero) with the exception of the 16 scratch registers, these power-up in an indeterminate state and should be initialized before they are used. all selectors can be read/written using the load/store scripts instruction, memory-to-memory move, read/write scripts instruction or cpu with scripts not running. note: crossing of selector boundaries in one memory operation is not supported. registers: 0xa0C0xa3 memory move read selector (mmrs) read/write supplies ad[63:32] during data read operations for memory-to-memory moves and absolute address load operations. a special mode of this register can be enabled by setting the pci con?guration info enable bit in the chip test two (ctest2) register. if this bit is set, the memory move read selector (mmrs) register returns bits [63:32] of the memory mapped operating register, pci base address register one (memory) , when read. writes to the mmrs register are unaffected. clearing the pci con?guration info enable bit causes the mmrs register to return to normal operation.
64-bit scripts selectors 4-107 registers: 0xa4C0xa7 memory move write selector (mmws) read/write supplies ad[63:32] during data write operations during memory-to-memory moves and absolute address store operations. a special mode of this register can be enabled by setting the pci con?guration info enable bit in the chip test two (ctest2) register. if this bit is set, the mmws register returns bits [63:32] of the scripts ram pci base address register two (scripts ram) in bits [31:0] of the mmws register when read. writes to the mmws register are unaffected. clearing the pci con?guration info enable bit causes the mmws register to return to normal operation. registers: 0xa8C0xab scripts fetch selector (sfs) read/write supplies ad[63:32] during scripts fetches and indirect fetches (excluding table indirect fetches). this register can be loaded automatically using a 64-bit jump instruction. a special mode of this register can be enabled by setting the pci con?guration info enable bit in the chip test two (ctest2) register. if this bit is set, bits [16:23] of the scripts fetch selector (sfs) register return the pci revision id (rev id) register value and bits [0:15] return the pci device id register value when read. writes to the scripts fetch selector (sfs) register are unaffected. clearing the pci con?guration information enable bit causes the sfs register to return to normal operation. registers: 0xacC0xaf dsa relative selector (drs) read/write supplies ad[63:32] during table indirect fetches and load/store data structure address (dsa) relative operations.
4-108 registers registers: 0xb0C0xb3 static block move selector (sbms) read/write supplies ad[63:32] during block move operations, reads or writes. this register is static and will not be changed when a 64-bit direct bmov is used. registers: 0xb4C0xb7 dynamic block move selector (dbms) read/write supplies ad[63:32] during block move operations, reads or writes. this register is used only during 64-bit direct bmov instructions and will be reloaded with the upper 32-bit data address upon execution of 64-bit direct bmovs. registers: 0xb8C0xbb dma next address 64 (dnad64) read/write this register holds the current selector being used in a given host transaction. the appropriate selector is copied to this register prior to beginning a host transaction. registers: 0xbcC0xbf reserved
phase mismatch jump registers 4-109 4.4 phase mismatch jump registers eight 32-bit registers contain the byte count and addressing information required to update the direct, indirect, or table indirect bmov instructions with new byte counts and addresses. the eight register descriptions follow. all registers can be read/written using the load/store scripts instructions, memory-to-memory moves, read/write scripts instructions, or the cpu with scripts not running. registers: 0xc0C0xc3 phase mismatch jump address 1 (pmjad1) read/write this register contains the 32-bit address that will be jumped to upon a phase mismatch. depending upon the state of the pmjctl bit this address will either be used during an outbound (data out, command, message out) phase mismatch (pmjctl = 0) or when the wsr bit is cleared (pmjctl = 1). it should be loaded with an address of a scripts routine that will handle the updating of memory data structures of the bmov that was executing when the phase mismatch occurred. registers: 0xc4C0xc7 phase mismatch jump address 2 (pmjad2) read/write this register contains the 32-bit address that will be jumped to upon a phase mismatch. depending upon the state of the pmjctl bit this address will either be used during an inbound (data in, status, message in) phase mismatch (pmjctl = 0) or when the wsr bit is set (pmjctl = 1). it should be loaded with an address of a scripts routine that will handle the updating of memory data structures of the bmov that was executing when the phase mismatch occurred.
4-110 registers registers: 0xc8C0xcb remaining byte count (rbc) read/write this register contains the byte count that remains for the bmov that was executing when the phase mismatch occurred. in the case of direct or indirect bmov instructions, the upper byte of this register will also contain the opcode of the bmov that was executing. in the case of a table indirect bmov instruction, the upper byte will contain the upper byte of the table indirect entry that was fetched. in the case of a scsi data receive, this byte count will re?ect all data received from the scsi bus, including any byte in scsi wide residue (swide) . there will be no data remaining in the part that must be ?ushed to memory with the exception of a possible byte in the swide register. that byte must be ?ushed to memory manually in scripts. in the case of a scsi data send, this byte count will re?ect all data sent out onto the scsi bus. any data left in the part from the phase mismatch will be ignored and automatically cleared from the fifos. registers: 0xccC0xcf updated address (ua) read/write this register will contain the updated data address for the bmov that was executing when the phase mismatch occurred. in the case of a scsi data receive, if there is a byte in the scsi wide residue (swide) register then this address will point to the location where that byte must be stored. the swide byte must be manually written to memory and this address must be incremented prior to updating any scatter/gather entry. in the case of a scsi data receive, if there is not a byte in the swide register then this address will be the next location that should be written to when this i/o restarts. no manual ?ushing will be necessary. in the case of a scsi data send, all data sent to the scsi bus will be accounted for and any data left in the part will be ignored and will be automatically cleared from the fifos.
phase mismatch jump registers 4-111 registers: 0xd0C0xd3 entry storage address (esa) read/write this register's value depends on the type of bmov being executed. the three types of bmovs are. registers: 0xd4C0xd7 instruction address (ia) read/write this register always contains the address of the bmov instruction that was executing when the phase mismatch occurred. this value will always match the value in the entry storage address (esa) except in the case of a table indirect bmov in which case the esa will have the address of the table indirect entry and this register will point to the address of the bmov instruction. registers: 0xd8C0xda scsi byte count (sbc) read only this register contains the count of the number of bytes transferred to or from the scsi bus during any given bmov. this value is used in calculating the information placed into the remaining byte count (rbc) and updated address (ua) registers and should not need to be used in normal operations. there are two conditions in which this byte count will not match the number of bytes transferred exactly. if a bmov is executed to transfer an odd number of bytes across a wide bus then the byte count at the end of the bmov will be greater than the number of bytes sent by one. this will also happen in an odd byte count wide receive case. also, in the case of a wide send in which there is a chain byte from a previous direct bmov: in the case of a direct bmov, this register will contain the address the bmov was fetched from when the phase mismatch occurred. indirect bmov: in the case of an indirect bmov, this register will contain the address the bmov was fetched from when the phase mismatch occurred. table indirect bmov: in the case of a table indirect bmov, this register will contain the address of the table indirect entry being used when the phase mismatch occurred.
4-112 registers transfer, the count will not re?ect the chain byte sent across the bus during that bmov. the reason for this is due to the fact that to determine the correct address to start fetching data from after a phase mismatch this byte cannot be counted for this bmov as it was actually part of the byte count for the previous bmov. register: 0xdb reserved registers: 0xdcC0xdf cumulative scsi byte count (csbc) read/write this loadable register contains a cumulative count of the actual number of bytes that have been transferred across the scsi bus during data phases, i.e. it will not count bytes sent in command, status, message in or message out phases. it will count bytes as long as the phase mismatch enable (enpmj) in the chip control 0 (ccntl0) register is set. unlike the scsi byte count (sbc) this count will not be cleared on each bmov instruction but will continue to count across multiple bmov instructions. this register can be loaded with any arbitrary start value. registers: 0xe0C0xff reserved
symbios SYM53C896 pci to dual channel ultra2 scsi multifunction controller 5-1 chapter 5 scsi scripts instruction set after power-up and initialization, the SYM53C896 can operate in the low level register interface mode, or use scsi scripts. with the low level register interface, the user has access to the dma control logic and the scsi bus control logic. an external processor has access to the scsi bus signals and the low level dma signals, which allow creation of complicated board level test algorithms. the low level interface is useful for backward compatibility with scsi devices that require certain unique timings or bus sequences to operate properly. another feature allowed at the low level is loopback testing. in loopback mode, the scsi core can be directed to talk to the dma core to test internal data paths all the way out to the chips pins. the following sections describe the bene?ts and use of scsi scripts. section 5.1, scsi scripts section 5.2, block move instructions section 5.3, i/o instructions section 5.4, read/write instructions section 5.5, transfer control instructions section 5.6, memory move instructions section 5.7, load/store instructions 5.1 scsi scripts to operate in the scsi scripts mode, the SYM53C896 requires only a scripts start address. the start address must be at a dword (four byte) boundary. this aligns all the following scripts at a dword boundary since all scripts are 8 or 12 bytes long. instructions are
5-2 scsi scripts instruction set fetched until an interrupt instruction is encountered, or until an unexpected event (such as a hardware error) causes an interrupt to the external processor. once an interrupt is generated, the SYM53C896 halts all operations until the interrupt is serviced. then, the start address of the next scripts instruction is written to the dma scripts pointer (dsp) register to restart the automatic fetching and execution of instructions. in the scsi scripts mode the SYM53C896 is allowed to make decisions based on the status of the scsi bus, which frees the microprocessor from servicing the numerous interrupts inherent in i/o operations. given the rich set of scsi oriented features included in the instruction set, and the ability to re-enter the scsi algorithm at any point, this high level interface is all that is required for both normal and exception conditions. switching to the low level mode for error recovery is not required. the following types of scripts instructions are implemented in the SYM53C896: block moveused to move data between the scsi bus and memory. i/o or read/writecauses the SYM53C896 to trigger common scsi hardware sequences, or to move registers. transfer controlallows scripts instructions to make decisions based on real time scsi bus conditions. memory movecauses the SYM53C896 to execute block moves between different parts of main memory. load/storeprovides a more ef?cient way to move data to/from memory from/to an internal register in the chip without using the memory move instruction. each instruction consists of two or three 32-bit words. the ?rst 32-bit word is always loaded into the dma command (dcmd) and dma byte counter (dbc) registers, the second into the dma scripts pointer save (dsps) register. the third word, used only by memory move instructions, is loaded into the temporary (temp) shadow register. in an indirect i/o or move instruction, the ?rst two 32-bit opcode fetches are followed by one or two more 32-bit fetch cycles.
scsi scripts 5-3 5.1.1 sample operation the following example describes execution of a scripts block move instruction. the host cpu, through programmed i/o, gives the dma scripts pointer (dsp) register (in the operating register ?le) the starting address in main memory that points to a scsi scripts program for execution. loading the dma scripts pointer (dsp) register causes the SYM53C896 to fetch its ?rst instruction at the address just loaded. this fetch is from main memory or the internal ram, depending on the address. the SYM53C896 typically fetches two dwords (64 bits) and decodes the high-order byte of the ?rst dword as a scripts instruction. if the instruction is a block move, the lower three bytes of the ?rst dword are stored and interpreted as the number of bytes to move. the second dword is stored and interpreted as the 32-bit beginning address in main memory to which the move is directed. for a scsi send operation, the SYM53C896 waits until there is enough space in the dma fifo to transfer a programmable size block of data. for a scsi receive operation, it waits until enough data is collected in the dma fifo for transfer to memory. at this point, the SYM53C896 requests use of the pci bus again to transfer the data. when the SYM53C896 is granted the pci bus, it executes (as a bus master) a burst transfer (programmable size) of data, decrements the internally stored remaining byte count, increments the address pointer, and then releases the pci bus. the SYM53C896 stays off the pci bus until the fifo can again hold (for a write) or has collected (for a read) enough data to repeat the process. the process repeats until the internally stored byte count has reached zero. the SYM53C896 releases the pci bus and then performs another scripts instruction fetch cycle, using the incremented stored address maintained in the dma scripts pointer (dsp) register. execution of scripts instructions continues until an error condition occurs or an interrupt scripts instruction is received. at this point, the SYM53C896 interrupts the host cpu and waits for further servicing by the host system. it can execute independent block move instructions specifying
5-4 scsi scripts instruction set new byte counts and starting locations in main memory. in this manner, the SYM53C896 performs scatter/gather operations on data without requiring help from the host program, generating a host interrupt, or programming of an external dma controller. figure 5.1 scripts overview 5.2 block move instructions for block move instructions, bits 5 and 4 (siom and diom) in the dma mode (dmode) register determine whether the source/destination address resides in memory or i/o space. when data is moved onto the scsi bus, siom controls whether that data comes from i/o or memory space. when data is moved off of the scsi bus, diom controls whether that data goes to i/o or memory space. system processor system memory (or internal ram) scsi initiator write example select atn0, alt_addr move 1, identify_msg_buf, when msg_out move 6, cmd_buf, when cmd move 512, data_buf, when data_out move 1, stat_in_buf, when status move 1, msg_in_buf, when msg_in move scntl2 & 7f to scntl2 clear ack wait disconnect alt2 int 10 data structure message buffer command buffer data buffer status buffer SYM53C896 scsi bus write dsp fetch scripts data (data is not fetched across system bus if internal ram is enabled.) s y s t e m b u s
block move instructions 5-5 5.2.1 first dword figure 5.2 block move instruction - first dword it[1:0] instruction type-block move [31:30] ia indirect addressing 29 direct when this bit is cleared, user data is moved to or from the 32-bit data start address for the block move instruction. the value is loaded into the chips address register and incremented as data is transferred. the address of the data to move is in the second dword of this instruction. when the en64dbmv bit in chip control 1 (ccntl1) is set, a third dword is fetched to provide the upper dword of a 64-bit address. the upper dword address will be fetched along with the instruction and loaded into the dynamic block move selector (dbms) register. if the en64dbmv bit is cleared, then the upper dword address is pulled from the static block move selector (sbms) register. the byte count and absolute address are as follows: indirect when set, the 32-bit user data start address for the block move is the address of a pointer to the actual data buffer address. the value at the 32-bit start address is loaded into the chips dma next address (dnad) register using a third dword fetch (4-byte transfer across the host computer bus). 31 30 29 28 27 26 24 23 0 dcmd register dbc register it[1:0] ia tia opc scsip[2:0] tc[23:0] command byte count lower dword address of data upper dword address of data (en64dbmv = 1)
5-6 scsi scripts instruction set use the fetched byte count, but fetch the data address from the address in the instruction. if 64-bit addressing is desired, the upper dword of the address is stored in the static block move selector (sbms) register. when the value in sbms is 0x0, 32-bit addressing is assumed. . once the data pointer address is loaded, it is executed as when the chip operates in the direct mode. this indirect feature allows speci?cation of a table of data buffer addresses. using the scsi scripts compiler, the table offset is placed in the scripts at compile time. then at the actual data transfer time, the offsets are added to the base address of the data address table by the external processor. the logical i/o driver builds a structure of addresses for an i/o rather than treating each address individually. note: using indirect and table indirect addressing simultaneously is not permitted; use only one addressing method at a time. tia table indirect 28 32-bit addressing when this bit is set, the 24-bit signed value in the start address of the move is treated as a relative displacement from the value in the data structure address (dsa) register. both the transfer count and the source/ destination address are fetched from this location. use the signed integer offset in bits [23:0] of the second four bytes of the instruction, added to the value in the data structure address (dsa) register, to fetch ?rst the byte count and then the data address. the signed value is combined with the data structure base address to generate the physical address used to fetch values from the data structure. sign-extended values of all ones for negative values are allowed, but bits [31:24] are ignored. . command byte count address of pointer to data command not used dont care table offset
block move instructions 5-7 note: using indirect and table indirect addressing simultaneously is not permitted; use only one addressing method at a time. prior to the start of an i/o, load the data structure address (dsa) register with the base address of the i/o data structure. any address on a dword boundary is allowed. after a table indirect opcode is fetched, the data structure address (dsa) is added to the 24-bit signed offset value from the opcode to generate the address of the required data; both positive and negative offsets are allowed. a subsequent fetch from that address brings the data values into the chip. for a move instruction, the 24-bit byte count is fetched from system memory. then the 32-bit physical address is brought into the SYM53C896. execution of the move begins at this point. scripts can directly execute operating system i/o data structures, saving time at the beginning of an i/o operation. the i/o data structure can begin on any dword boundary and may cross system segment boundaries. there are two restrictions on the placement of pointer data in system memory: the eight bytes of data in the move instruction must be contiguous, as shown below, and indirect data fetches are not available during execution of a memory-to-memory dma operation . 64-bit addressing if the enable 64-bit table indirect block move (en64tibmv) bit is clear, then table indirect block moves will remain as 2 dword opcodes plus a 2 dword table entry and the upper 32 bits of the address will be pulled from the static block move selector (sbms) (which is loaded manually) when doing data transfers during block move operations. 00 byte count physical data address
5-8 scsi scripts instruction set if the enable 64-bit table indirect block move (en64tibmv) bit is set and the 64-bit table indirect index mode (64timod) bit is cleared, then bits [28:24] of the ?rst dword of the table entry (where the byte count is located) will select one of the 16 scratch registers or any of the six 64-bit selector registers (for a total of 22 selector choices) as a selector for the upper 32-bit address. please see the table indirect index mode mapping table for a breakdown of index values and the corresponding registers selected. the selected address will get loaded into the dma next address 64 (dnad64) automatically. note: if en64tibmv is set and 64timod is set then bits [31:24] of the ?rst dword of the table entry (where the byte count is located) will be loaded directly into dma next address 64 (dnad64) to provide a 40-bit address. the format for the table indirect entries for each mode is shown below. the table for table indirect block moves upper 32-bit address locations summarizes the available modes for table indirect block moves. index mode 0 (64timod clear) table entry format: index mode 1 (64timod set) table entry format: table indirect block moves upper 32-bit address locations: 31 29 28 24 23 0 r sel index byte count source/destination address [31:0] 31 24 23 0 src/dest addr [39:32] byte count source/destination address [31:0]
block move instructions 5-9 table indirect index mode mapping: en64tibmv 64timod upper 32 bit data address comes from 0 0 sbms 0 1 sbms 1 0 scratchcCj, mmws, mmrs, sfs, drs, sbms, dbms 1 1 1st table entry dword bits 24C31 (40-bit addressing only) index value selector used 0x00 scratch c 0x01 scratch d 0x02 scratch e 0x03 scratch f 0x04 scratch g 0x05 scratch h 0x06 scratch i 0x07 scratch j 0x08 scratch k 0x09 scratch l 0x0a scratch m 0x0b scratch n 0x0c scratch o 0x0d scratch p 0x0e scratch q 0x0f scratch r 0x10 mmrs 0x11 mmws 0x12 sfs
5-10 scsi scripts instruction set opc opcode 27 this 1-bit ?eld de?nes the instruction to execute as a block move (move). target mode the SYM53C896 veri?es that it is connected to the scsi bus as a target before executing this instruction. the SYM53C896 asserts the scsi phase signals (smsg/, sc_d/, and si_o/) as de?ned by the phase field bits in the instruction. if the instruction is for the command phase, the SYM53C896 receives the ?rst command byte and decodes its scsi group code. if the scsi group code is either group 0, group 1, group 2, or group 5, then the SYM53C896 overwrites the dma byte counter (dbc) register with the length of the command descriptor block: 6, 10, or 12 bytes. if the vendor unique enhancement 0 (vue0) bit ( scsi control two (scntl2) , bit 1) is cleared and the scsi group code is a vendor unique code, the SYM53C896 overwrites the dma byte counter (dbc) register with the length of the command descriptor block: 6, 10, or 12 bytes. if the vue0 bit is set, the SYM53C896 receives the number of bytes in the byte count regardless of the group code. 0x13 drs 0x14 sbms 0x15 dbms 0x16C0x1f illegal (will result in iid interrupt) index value selector used opc instruction de?ned 0 move/move64 1 chmov/chmov64
block move instructions 5-11 if any other group code is received, the dma byte counter (dbc) register is not modi?ed and the SYM53C896 requests the number of bytes speci?ed in the dma byte counter (dbc) register. if the dbc register contains 0x000000, an illegal instruction interrupt is generated. the SYM53C896 transfers the number of bytes speci?ed in the dma byte counter (dbc) register starting at the address speci?ed in the dma next address (dnad) register. if the opcode bit is set and a data transfer ends on an odd byte boundary, the SYM53C896 stores the last byte in the scsi wide residue (swide) register during a receive operation. this byte is combined with the ?rst byte from the subsequent transfer so that a wide transfer can complete. if the satn/ signal is asserted by the initiator or a parity error occurred during the transfer, it is possible to halt the transfer and generate an interrupt. the disable halt on parity error or atn bit in the scsi control one (scntl1) register controls whether the SYM53C896 halts on these conditions immediately, or waits until completion of the current move. initiator mode the SYM53C896 veri?es that it is connected to the scsi bus as an initiator before executing this instruction. the SYM53C896 waits for an unserviced phase to occur. an unserviced phase is de?ned as any phase (with sreq/ asserted) for which the SYM53C896 has not yet transferred data by responding with a sack/. the SYM53C896 compares the scsi phase bits in the dma command (dcmd) register with the latched scsi phase lines stored in the scsi status one (sstat1) register. these phase lines are latched when sreq/ is asserted. opc instruction de?ned 0 chmov/chmov64 1 move/move64
5-12 scsi scripts instruction set if the scsi phase bits match the value stored in the scsi status one (sstat1) register, the SYM53C896 transfers the number of bytes speci?ed in the dma byte counter (dbc) register starting at the address pointed to by the dma next address (dnad) register. if the opcode bit is cleared and a data transfer ends on an odd byte boundary, the SYM53C896 stores the last byte in the scsi wide residue (swide) register during a receive operation, or in the scsi output data latch (sodl) register during a send operation. this byte is combined with the ?rst byte from the subsequent transfer so that a wide transfer can complete. if the scsi phase bits do not match the value stored in the scsi status one (sstat1) register, the SYM53C896 generates a phase mismatch interrupt and the instruction is not executed. during a message-out phase, after the SYM53C896 has performed a select with attention (or satn/ is manually asserted with a set atn instruction), the SYM53C896 deasserts satn/ during the ?nal sreq/sack/ handshake. when the SYM53C896 is performing a block move for message-in phase, it does not deassert the sack/ signal for the last sreq/sack/ handshake. clear the sack/ signal using the clear sack i/o instruction. scsip[2:0] scsi phase [26:24] this 3-bit ?eld de?nes the desired scsi information transfer phase. when the SYM53C896 operates in the initiator mode, these bits are compared with the latched scsi phase bits in the scsi status one (sstat1) register. when the SYM53C896 operates in the target mode, it asserts the phase de?ned in this ?eld. the following table describes the possible combinations and the corresponding scsi phase.
block move instructions 5-13 tc[23:0] transfer counter [23:0] this 24-bit ?eld speci?es the number of data bytes to be moved between the SYM53C896 and system memory. the ?eld is stored in the dma byte counter (dbc) register. when the SYM53C896 transfers data to/from memory, the dbc register is decremented by the number of bytes transferred. in addition, the dma next address (dnad) register is incremented by the number of bytes transferred. this process is repeated until the dbc register is decremented to zero. at this time, the SYM53C896 fetches the next instruction. if bit 28 is set, indicating table indirect addressing, this ?eld is not used. the byte count is instead fetched from a table pointed to by the data structure address (dsa) register. msg c_d i_o scsi phase 0 0 0 data-out 0 0 1 data-in 0 1 0 command 0 1 1 status 1 0 0 reserved-out 1 0 1 reserved-in 1 1 0 message-out 1 1 1 message-in
5-14 scsi scripts instruction set 5.2.2 second dword figure 5.3 block move instruction - second dword start address [31:0] this 32-bit ?eld speci?es the starting address of the data to move to/from memory. this ?eld is copied to the dma next address (dnad) register. when the SYM53C896 transfers data to or from memory, the dnad register is incremented by the number of bytes transferred. when bit 29 is set, indicating indirect addressing, this address is a pointer to an address in memory that points to the data location. when bit 28 is set, indicating table indirect addressing, the value in this ?eld is an offset into a table pointed to by the data structure address (dsa) . the table entry contains byte count and address information. 5.2.3 third dword figure 5.4 block move instruction - third dword start address [63:32] this 32-bit ?eld speci?es the upper dword of a 64-bit starting address of data to move to/from memory. this ?eld is copied to the dynamic block move selector (dbms) register. the en64dbmv bit in the chip control 1 (ccntl1) register must be set for this dword to be fetched. 31 24 23 16 15 8 7 0 dsps register 31 24 23 16 15 8 7 0 dbms register
i/o instructions 5-15 5.3 i/o instructions this section contains information about the i/o instruction register. it is divided into first dword and second dword . 5.3.1 first dword figure 5.5 first 32-bit word of the i/o instruction it[1:0] instruction type - i/o instruction [31:30] opc[2:0] opcode [29:27] the following opcode bits have different meanings, depending on whether the SYM53C896 is operating in the initiator or target mode. opcode selections 0b101C 0b111 are considered read/write instructions, and are described section 5.4, read/write instructions . target mode reselect instruction the SYM53C896 arbitrates for the scsi bus by asserting the scsi id stored in the scsi chip id (scid) register. if it loses arbitration, it tries again during the next available arbitration cycle without reporting any lost arbitration status. if the SYM53C896 wins arbitration, it attempts to reselect the scsi device whose id is de?ned in the destination id ?eld of the instruction. once the SYM53C896 wins 31 30 29 27 26 25 24 23 20 19 16 15 11 10 9 8 7 6 5 4 3 2 0 dcmd register dbc register it[1:0] opc[2:0] ra ti sel r endid[3:0] rcatm ra r at n r opc2 opc1 opc0 instruction de?ned 0 0 0 reselect 0 0 1 disconnect 0 1 0 wait select 011set 1 0 0 clear
5-16 scsi scripts instruction set arbitration, it fetches the next instruction from the address pointed to by the dma scripts pointer (dsp) register. this way the scripts can move on to the next instruction before the reselection completes. it continues executing scripts until a scripts that requires a response from the initiator is encountered. if the SYM53C896 is selected or reselected before winning arbitration, it fetches the next instruction from the address pointed to by the 32-bit jump address ?eld stored in the dma next address (dnad) register. manually set the SYM53C896 to the initiator mode if it is reselected, or to the target mode if it is selected. disconnect instruction the SYM53C896 disconnects from the scsi bus by deasserting all scsi signal outputs. wait select instruction if the SYM53C896 is selected, it fetches the next instruction from the address pointed to by the dma scripts pointer (dsp) register. if reselected, the SYM53C896 fetches the next instruction from the address pointed to by the 32-bit jump address ?eld stored in the dma next address (dnad) register. manually set the SYM53C896 to the initiator mode when it is reselected. if the cpu sets the sigp bit in the interrupt status zero (istat0) register, the SYM53C896 aborts the wait select instruction and fetches the next instruction from the address pointed to by the 32-bit jump address ?eld stored in the dma next address (dnad) register. set instruction when the sack/ or satn/ bits are set, the corresponding bits in the scsi output control latch (socl) register are set. do not set sack/ or satn/ except for testing purposes. when the target bit is set, the corresponding bit in the scsi control zero (scntl0) register is also set. when the carry bit is set, the corresponding bit in the arithmetic logic unit (alu) is set. note: none of the signals are set on the scsi bus in target mode.
i/o instructions 5-17 clear instruction when the sack/ or satn/ bits are cleared, the corresponding bits are cleared in the scsi output control latch (socl) register. do not set sack/ or satn/ except for testing purposes. when the target bit is cleared, the corresponding bit in the scsi control zero (scntl0) register is cleared. when the carry bit is cleared, the corresponding bit in the alu is cleared. note: none of the signals are cleared on the scsi bus in the target mode. initiator mode select instruction the SYM53C896 arbitrates for the scsi bus by asserting the scsi id stored in the scsi chip id (scid) register. if it loses arbitration, it tries again during the next available arbitration cycle without reporting any lost arbitration status. if the SYM53C896 wins arbitration, it attempts to select the scsi device whose id is de?ned in the destination id ?eld of the instruction. once the SYM53C896 wins arbitration, it fetches the next instruction from the address pointed to by the dma scripts pointer (dsp) register. this way the scripts can move to the next instruction before the selection completes. it continues executing scripts until a scripts that requires a response from the target is encountered. if the SYM53C896 is selected or reselected before winning arbitration, it fetches the next instruction from the address pointed to by the 32-bit jump address ?eld stored opc2 opc1 opc0 instruction de?ned 0 0 0 select 0 0 1 wait disconnect 0 1 0 wait reselect 0 1 1 set 1 0 0 clear
5-18 scsi scripts instruction set in the dma next address (dnad) register. manually set the SYM53C896 to the initiator mode if it is reselected, or to the target mode if it is selected. if the select with satn/ ?eld is set, the satn/ signal is asserted during the selection phase. wait disconnect instruction the SYM53C896 waits for the target to perform a legal disconnect from the scsi bus. a legal disconnect occurs when sbsy/ and ssel/ are inactive for a minimum of one bus free delay (400 ns), after the SYM53C896 receives a disconnect message or a command complete message. wait reselect instruction if the SYM53C896 is selected before being reselected, it fetches the next instruction from the address pointed to by the 32-bit jump address ?eld stored in the dma next address (dnad) register. manually set the SYM53C896 to the target mode when it is selected. if the SYM53C896 is reselected, it fetches the next instruction from the address pointed to by the dma scripts pointer (dsp) register. if the cpu sets the sigp bit in the interrupt status zero (istat0) register, the SYM53C896 aborts the wait reselect instruction and fetches the next instruction from the address pointed to by the 32-bit jump address ?eld stored in the dma next address (dnad) register. set instruction when the sack/ or satn/ bits are set, the corresponding bits in the scsi output control latch (socl) register are set. when the target bit is set, the corresponding bit in the scsi control zero (scntl0) register is also set. when the carry bit is set, the corresponding bit in the alu is set. clear instruction when the sack/ or satn/ bits are cleared, the corresponding bits are cleared in the scsi output control latch (socl) register. when the target bit is cleared, the
i/o instructions 5-19 corresponding bit in the scsi control zero (scntl0) register is cleared. when the carry bit is cleared, the corresponding bit in the alu is cleared. ra relative addressing mode 26 when this bit is set, the 24-bit signed value in the dma next address (dnad) register is used as a relative displacement from the current dma scripts pointer (dsp) address. use this bit only in conjunction with the select, reselect, wait select, and wait reselect instructions. the select and reselect instructions can contain an absolute alternate jump address or a relative transfer address. ti table indirect mode 25 when this bit is set, the 24-bit signed value in the dma byte counter (dbc) register is added to the value in the data structure address (dsa) register, and used as an offset relative to the value in the data structure address (dsa) register. the scsi control three (scntl3) value, scsi id, synchronous offset and synchronous period are loaded from this address. prior to the start of an i/o, load the data structure address (dsa) with the base address of the i/o data structure. any address on a dword boundary is allowed. after a table indirect opcode is fetched, the data structure address (dsa) is added to the 24-bit signed offset value from the opcode to generate the address of the required data. both positive and negative offsets are allowed. a subsequent fetch from that address brings the data values into the chip. scripts can directly execute operating system i/o data structures, saving time at the beginning of an i/o operation. the i/o data structure can begin on any dword boundary and may cross system segment boundaries. there are two restrictions on the placement of data in system memory: the i/o data structure must lie within the 8 mbytes above or below the base address. an i/o command structure must have all four bytes contiguous in system memory, as shown below. the offset/period bits are ordered as in the scsi transfer (sxfer) register. the con?guration bits are ordered as in the scsi control three (scntl3) register.
5-20 scsi scripts instruction set use this bit only in conjunction with the select, reselect, wait select, and wait reselect instructions. it is allowable to set bits 25 and 26 individually or in combination: direct uses the device id and physical address in the instruction. table indirect uses the physical jump address, but fetches data using the table indirect method. relative uses the device id in the instruction, but treats the alternate address as a relative jump. table relative treats the alternate jump address as a relative jump and fetches the device id, synchronous offset, and synchronous period indirectly. the value in bits [23:0] of con?g id offset/period 00 bit 25 bit 26 direct 0 0 table indirect 0 1 relative 1 0 table relative 1 1 command id not used not used absolute alternate address command table offset absolute alternate address command id not used not used absolute jump offset
i/o instructions 5-21 the ?rst four bytes of the scripts instruction is added to the data structure base address to form the fetch address. sel select with atn/ 24 this bit speci?es whether satn/ is asserted during the selection phase when the SYM53C896 is executing a select instruction. when operating in the initiator mode, set this bit for the select instruction. if this bit is set on any other i/o instruction, an illegal instruction interrupt is generated. r reserved [23:20] endid[3:0] encoded scsi destination id [19:16] this 4-bit ?eld speci?es the destination scsi id for an i/o instruction. r reserved [15:11] ca set/clear carry 10 this bit is used in conjunction with a set or clear instruction to set or clear the carry bit. setting this bit with a set instruction asserts the carry bit in the alu. clearing this bit with a clear instruction deasserts the carry bit in the alu. tm set/clear target mode 9 this bit is used in conjunction with a set or clear instruction to set or clear the target mode. setting this bit with a set instruction con?gures the SYM53C896 as a target device (this sets bit 0 of the scsi control zero (scntl0) register). clearing this bit with a clear instruction con?gures the SYM53C896 as an initiator device (this clears bit 0 of the scntl0 register). r reserved [8:7] a set/clear sack/ 6 r reserved [5:4] command table offset alternate jump offset
5-22 scsi scripts instruction set atn set/clear satn/ 3 these two bits are used in conjunction with a set or clear instruction to assert or deassert the corresponding scsi control signal. bit 6 controls the scsi sack/ signal. bit 3 controls the scsi satn/ signal. the set instruction is used to assert sack/ and/or satn/ on the scsi bus. the clear instruction is used to deassert sack/ and/or satn/ on the scsi bus. the corresponding bit in the scsi output control latch (socl) register will be set or cleared depending on the instruction used. since sack/ and satn/ are initiator signals, they are not asserted on the scsi bus unless the SYM53C896 is operating as an initiator or the scsi loopback enable bit is set in the scsi test two (stest2) register. the set/clear scsi ack/, atn/ instruction is used after message phase block move operations to give the initiator the opportunity to assert attention before acknowledging the last message byte. for example, if the initiator wishes to reject a message, it issues an assert scsi atn instruction before a clear scsi ack instruction. r reserved [2:0] 5.3.2 second dword figure 5.6 second 32-bit word of the i/o instruction sa start address [31:0] this 32-bit ?eld contains the memory address to fetch the next instruction if the selection or reselection fails. if relative or table relative addressing is used, this value is a 24-bit signed offset relative to the current dma scripts pointer (dsp) register value. 31 24 23 16 15 8 7 0 dsps register
read/write instructions 5-23 5.4 read/write instructions the read/write instruction supports addition, subtraction, and comparison of two separate values within the chip. it performs the desired operation on the speci?ed register and the scsi first byte received (sfbr) register, then stores the result back to the speci?ed register or the sfbr. if the com bit ( dma control (dcntl) , bit 0) is cleared, read/write instructions cannot be used. 5.4.1 first dword figure 5.7 read/write instruction - first dword it[1:0] instruction type - read/write instruction [31:30] the read/write instruction uses operator bits [26:24] in conjunction with the opcode bits to determine which instruction is currently selected. opc[2:0] opcode [29:27] the combinations of these bits determine if the instruction is a read/write or an i/o instruction. opcodes 0b000 through 0b100 are considered i/o instructions. o[2:0] operator [26:24] these bits are used in conjunction with the opcode bits to determine which instruction is currently selected. refer to table 5.1 for ?eld de?nitions. d8 use data8/sfbr 23 when this bit is set, scsi first byte received (sfbr) is used instead of the data8 value during a read-modify- write instruction (see table 5.1 ). this allows the user to add two register values. a[6:0] register address - a[6:0] [22:16] it is possible to change register values from scripts in read-modify-write cycles or move to/from scsi first byte received (sfbr) cycles. a[6:0] selects an 8-bit source/destination register within the SYM53C896. 31 30 29 27 26 24 23 22 16 15 8 7 6 0 dcmd register dbc register it[1:0] opc[2:0] o[2:0] d8 a[6:0] immd a7 r-must be 0
5-24 scsi scripts instruction set immd immediate data [15:8] this 8-bit value is used as a second operand in logical and arithmetic functions. a7 upper register address line [a7] 7 this bit is used to access registers 0x80C0xff. r reserved [6:0] 5.4.2 second dword figure 5.8 read/write instruction - second dword da destination address [31:0] this ?eld contains the 32-bit destination address where the data is to move. 5.4.3 read-modify-write cycles during these cycles the register is read, the selected operation is performed, and the result is written back to the source register. the add operation is used to increment or decrement register values (or memory values if used in conjunction with a memory-to-register move operation) for use as loop counters. subtraction is not available when scsi first byte received (sfbr) is used instead of data8 in the instruction syntax. to subtract one value from another when using sfbr, ?rst xor the value to subtract (subtrahend) with 0xff, and add 1 to the resulting value. this creates the 2s compliment of the subtrahend. the two values are then added to obtain the difference. 5.4.4 move to/from sfbr cycles all operations are read-modify-writes as shown in table 5.1 . however, two registers are involved, one of which is always the scsi first byte received (sfbr) . the possible functions of this instruction are: 31 24 23 16 15 8 7 0 dsps register
read/write instructions 5-25 write one byte (value contained within the scripts instruction) into any chip register. move to/from the scsi first byte received (sfbr) from/to any other register. alter the value of a register with and, or, add, xor, shift left, or shift right operators. after moving values to the scsi first byte received (sfbr) , the compare and jump, call, or similar instructions are used to check the value. a move-to-sfbr followed by a move-from-sfbr is used to perform a register to register move. table 5.1 read/write instructions operator opcode 111 read-modify-write opcode 110 move to sfbr opcode 101 move from sfbr 000 move data into register. syntax: move data8 to rega move data into scsi first byte received (sfbr) register. syntax: move data8 to sfbr move data into register. syntax: move data8 to rega 001 1 shift register one bit to the left and place the result in the same register. syntax: move rega shl rega shift register one bit to the left and place the result in the scsi first byte received (sfbr) register. syntax: move rega shl sfbr shift the sfbr register one bit to the left and place the result in the register. syntax: move sfbr shl rega 010 or data with register and place the result in the same register. syntax: move rega | data8 to rega or data with register and place the result in the scsi first byte received (sfbr) register. syntax: move rega | data8 to sfbr or data with sfbr and place the result in the register. syntax: move sfbr | data8 to rega 011 xor data with register and place the result in the same register. syntax: move rega xor data8 to rega xor data with register and place the result in the scsi first byte received (sfbr) register. syntax: move rega xor data8 to sfbr xor data with sfbr and place the result in the register. syntax: move sfbr xor data8 to rega 100 and data with register and place the result in the same register. syntax: move rega & data8 to rega and data with register and place the result in the scsi first byte received (sfbr) register. syntax: move rega & data8 to sfbr and data with sfbr and place the result in the register. syntax: move sfbr & data8 to rega
5-26 scsi scripts instruction set miscellaneous notes: substitute the desired register name or address for rega in the syntax examples. data8 indicates eight bits of data. use sfbr instead of data8 to add two register values. 101 1 shift register one bit to the right and place the result in the same register. syntax: move rega shr rega shift register one bit to the right and place the result in the scsi first byte received (sfbr) register. syntax: move rega shr sfbr shift the sfbr register one bit to the right and place the result in the register. syntax: move sfbr shr rega 110 add data to register without carry and place the result in the same register. syntax: move rega + data8 to rega add data to register without carry and place the result in the scsi first byte received (sfbr) register. syntax: move rega + data8 to sfbr add data to sfbr without carry and place the result in the register. syntax: move sfbr + data8 to rega 111 add data to register with carry and place the result in the same register. syntax: move rega + data8 to rega with carry add data to register with carry and place the result in the scsi first byte received (sfbr) register. syntax: move rega + data8 to sfbr with carry add data to sfbr with carry and place the result in the register. syntax: move sfbr + data8 to rega with carry 1. data is shifted through the carry bit and the carry bit is shifted into the data byte. table 5.1 read/write instructions (cont.) operator opcode 111 read-modify-write opcode 110 move to sfbr opcode 101 move from sfbr
transfer control instructions 5-27 5.5 transfer control instructions this section describes transfer control instructions for the first dword , second dword , and third dword . 5.5.1 first dword figure 5.9 transfer control instructions - first dword it[1:0] instruction type - transfer control instruction [31:30] opc[2:0] opcode [29:27] this 3-bit ?eld speci?es the type of transfer control instruction to execute. all transfer control instructions can be conditional. they can be dependent on a true/false comparison of the alu carry bit or a comparison of the scsi information transfer phase with the phase ?eld, and/or a comparison of the first byte received with the data compare ?eld. each instruction can operate in the initiator or target mode. jump instruction the SYM53C896 can do a true/false comparison of the alu carry bit, or compare the phase and/or data as de?ned by the phase compare, data compare and true/false bit ?elds. if the comparisons are true, then it loads the dma scripts pointer (dsp) register with the contents of the dma scripts pointer save (dsps) 31 30 29 27 26 24 23 22 21 20 19 18 17 16 15 8 7 0 dcmd register dbc register it[1:0] opc[2:0] scsip[2:0] ra j ct if tf cd cp vp mc dc opc2 opc1 opc0 instruction de?ned 0 0 0 jump 0 0 1 call 0 1 0 return 0 1 1 interrupt 1 x x reserved
5-28 scsi scripts instruction set register. the dsp register now contains the address of the next instruction. if the comparisons are false, the SYM53C896 fetches the next instruction from the address pointed to by the dma scripts pointer (dsp) register, leaving the instruction pointer unchanged. when the jump64 instruction is used, a third dword is fetched and loaded into the scripts fetch selector (sfs) register. bit 22 indicates whether the jump is to a 32-bit address (0) or a 64-bit address (1). all combinations of jumps are still valid for jump64. call instruction the SYM53C896 can do a true/false comparison of the alu carry bit, or compare the phase and/or data as de?ned by the phase compare, data compare, and true/false bit ?elds. if the comparisons are true, it loads the dma scripts pointer (dsp) register with the contents of the dma scripts pointer save (dsps) register and that address value becomes the address of the next instruction. when the SYM53C896 executes a call instruction, the instruction pointer contained in the dma scripts pointer (dsp) register is stored in the temporary (temp) register. since the temp register is not a stack and can only hold one dword, nested call instructions are not allowed. if the comparisons are false, the SYM53C896 fetches the next instruction from the address pointed to by the dma scripts pointer (dsp) register and the instruction pointer is not modi?ed. return instruction the SYM53C896 can do a true/false comparison of the alu carry bit, or compare the phase and/or data as de?ned by the phase compare, data compare, and true/false bit ?elds. if the comparisons are true, it loads the dma scripts pointer (dsp) register with the contents of the dma scripts pointer save (dsps) register. that address value becomes the address of the next instruction.
transfer control instructions 5-29 when a return instruction is executed, the value stored in the temporary (temp) register is returned to the dma scripts pointer (dsp) register. the SYM53C896 does not check to see whether the call instruction has already been executed. it does not generate an interrupt if a return instruction is executed without previously executing a call instruction. if the comparisons are false, the SYM53C896 fetches the next instruction from the address pointed to by the dma scripts pointer (dsp) register and the instruction pointer is not modi?ed. interrupt instruction the SYM53C896 can do a true/false comparison of the alu carry bit, or compare the phase and/or data as de?ned by the phase compare, data compare, and true/false bit ?elds. if the comparisons are true, the SYM53C896 generates an interrupt by asserting the irq/ signal. the 32-bit address ?eld stored in the dma scripts pointer save (dsps) register can contain a unique interrupt service vector. when servicing the interrupt, this unique status code allows the interrupt service routine to quickly identify the point at which the interrupt occurred. the SYM53C896 halts and the dma scripts pointer (dsp) register must be written to before starting any further operation. interrupt-on-the-fly instruction the SYM53C896 can do a true/false comparison of the alu carry bit or compare the phase and/or data as de?ned by the phase compare, data compare, and true/false bit ?elds. if the comparisons are true, and the interrupt-on-the-fly bit interrupt status zero (istat0) bit 2) is set, the SYM53C896 asserts the interrupt-on-the-fly bit. scsip[2:0] scsi phase [26:24] this 3-bit ?eld corresponds to the three scsi bus phase signals that are compared with the phase lines latched when sreq/ is asserted. comparisons can be performed to determine the scsi phase actually being driven on the
5-30 scsi scripts instruction set scsi bus. the following table describes the possible combinations and their corresponding scsi phase. these bits are only valid when the SYM53C896 is operating in the initiator mode. clear these bits when the SYM53C896 is operating in the target mode. ra relative addressing mode 23 when this bit is set, the 24-bit signed value in the dma scripts pointer save (dsps) register is used as a relative offset from the current dma scripts pointer (dsp) address (which is pointing to the next instruction, not the one currently executing). the relative mode does not apply to return and interrupt scripts. jump/call an absolute address start execution at the new absolute address. jump/call a relative address start execution at the current address plus (or minus) the relative offset. the scripts program counter is a 32-bit value pointing to the scripts currently under execution by the SYM53C896. the next address is formed by adding the msg c/d i/o scsi phase 000 data-out 001 data-in 010 command 011 status 100 reserved-out 101 reserved-in 110 message-out 111 message-in command condition codes absolute alternate address command condition codes dont care alternate jump offset
transfer control instructions 5-31 32-bit program counter to the 24-bit signed value of the last 24 bits of the jump or call instruction. because it is signed (twos compliment), the jump can be forward or backward. a relative transfer can be to any address within a 16 mbyte segment. the program counter is combined with the 24-bit signed offset (using addition or subtraction) to form the new execution address. scripts programs may contain a mixture of direct jumps and relative jumps to provide maximum versatility when writing scripts. for example, major sections of code can be accessed with far calls using the 32-bit physical address, then local labels can be called using relative transfers. if a scripts is written using only relative transfers it does not require any run time alteration of physical addresses, and can be stored in and executed from a prom. j 32/64 bit jump 22 when this bit is cleared, the jump address is 32 bits wide. when this bit is set, the jump address is 64 bits wide. ct carry test 21 when this bit is set, decisions based on the alu carry bit can be made. true/false comparisons are legal, but data compare and phase compare are illegal. if interrupt-on-the-fly 20 when this bit is set, the interrupt instruction does not halt the scripts processor. once the interrupt occurs, the interrupt-on-the-fly bit ( interrupt status zero (istat0) bit 2) is asserted. tf jump if true/false 19 this bit determines whether the SYM53C896 branches when a comparison is true or when a comparison is false. this bit applies to phase compares, data compares, and carry tests. if both the phase compare and data compare bits are set, then both compares must be true to branch on a true condition. both compares must be false to branch on a false condition.
5-32 scsi scripts instruction set cd compare data 18 when this bit is set, the ?rst byte received from the scsi data bus (contained in the scsi first byte received (sfbr) register) is compared with the data to be compared field in the transfer control instruction. the wait for valid phase bit controls when this compare occurs. the jump if true/false bit determines the condition (true or false) to branch on. cp compare phase 17 when the SYM53C896 is in the initiator mode, this bit controls phase compare operations. when this bit is set, the scsi phase signals (latched by sreq/) are compared to the phase field in the transfer control instruction. if they match, the comparison is true. the wait for valid phase bit controls when the compare occurs. when the SYM53C896 is operating in the target mode and this bit is set it tests for an active scsi satn/ signal. vp wait for valid phase 16 if the wait for valid phase bit is set, the SYM53C896 waits for a previously unserviced phase before comparing the scsi phase and data. if the wait for valid phase bit is cleared, the SYM53C896 compares the scsi phase and data immediately. mc data compare mask [15:8] the data compare mask allows a scripts to test certain bits within a data byte. during the data compare, if any mask bits are set, the corresponding bit in the scsi first byte received (sfbr) data byte is ignored. for instance, a mask of 0b01111111 and data compare value of 0b1xxxxxxx allows the scripts processor to determine whether or not the high-order bit is set while ignoring the remaining bits. bit 19 result of compare action 0 false jump taken 0 true no jump 1 false no jump 1 true jump taken
transfer control instructions 5-33 dc data compare value [7:0] this 8-bit ?eld is the data compared against the scsi first byte received (sfbr) register. these bits are used in conjunction with the data compare mask field to test for a particular data value. if the com bit ( dma control (dcntl) , bit 0) is cleared, the value in the sfbr register may not be stable. in this case, do not use instructions using this data compare value. 5.5.2 second dword figure 5.10 transfer control instructions - second dword jump address [31:0] this 32-bit ?eld contains the address of the next instruction to fetch when a jump is taken. once the SYM53C896 fetches the instruction from the address pointed to by these 32 bits, this address is incremented by 4, loaded into the dma scripts pointer (dsp) register and becomes the current instruction pointer. 5.5.3 third dword figure 5.11 transfer control instructions - third dword jump64 address [31:0] this 32-bit ?eld contains the upper dword of a 64-bit address of the next instruction to fetch when a jump64 is taken. 31 24 23 16 15 8 7 0 dsps register 31 24 23 16 15 8 7 0 sfs register (used for jump64 instruction)
5-34 scsi scripts instruction set 5.6 memory move instructions for memory move instructions, bits 5 and 4 (siom and diom) in the dma mode (dmode) register determine whether the source or destination addresses reside in memory or i/o space. by setting these bits appropriately, data may be moved within memory space, within i/o space, or between the two address spaces. the memory move instruction is used to copy the speci?ed number of bytes from the source address to the destination address. for memory moves where the data read is from the 64-bit address space, the upper dword of the address resides in the memory move read selector (mmrs) register. for memory moves where the data is written to the 64-bit address space, the upper dword of the address resides in the memory move write selector (mmws) register. allowing the SYM53C896 to perform memory moves frees the system processor for other tasks and moves data at higher speeds than available from current dma controllers. up to 16 mbytes may be transferred with one instruction. there are two restrictions: both the source and destination addresses must start with the same address alignment (a[1:0]) must be the same). if the source and destination are not aligned, then an illegal instruction interrupt occurs. for the pci cache line size register setting to take effect, the source and destination must be the same distance from a cache line boundary. indirect addresses are not allowed. a burst of data is fetched from the source address, put into the dma fifo and then written out to the destination address. the move continues until the byte count decrements to zero, then another scripts is fetched from system memory. the dma scripts pointer save (dsps) and data structure address (dsa) registers are additional holding registers used during the memory move. however, the contents of the data structure address (dsa) register are preserved.
memory move instructions 5-35 5.6.1 first dword figure 5.12 memory move instructions - first dword it[2:0] instruction type - memory move [31:29] r reserved [28:25] these bits are reserved and must be zero. if any of these bits are set, an illegal instruction interrupt occurs. nf no flush 24 when this bit is set, the SYM53C896 performs a memory move without ?ushing the prefetch unit. when this bit is cleared, the memory move instruction automatically ?ushes the prefetch unit. use the no flush option if the source and destination are not within four instructions of the current memory move instruction. note: this bit has no effect unless the prefetch enable bit in the dma control (dcntl) register is set. for information on scripts instruction prefetching, see chapter 2, "functional description" . tc[23:0] transfer count [23:0] the number of bytes to transfer is stored in the lower 24 bits of the ?rst instruction word. 5.6.2 read/write system memory from a scripts by using the memory move instruction, single or multiple register values are transferred to or from system memory. because the SYM53C896 responds to addresses as de?ned in the base address register zero (i/o) or base address register one (memory) registers, it can be accessed during a memory move operation if the source or destination address decodes to within the chips register space. if this occurs, the register indicated by the lower seven bits of the address is taken as the data source or destination. in this way, register values are 31 29 28 25 24 23 16 15 8 7 0 dcmd register dbc register it[2:0] r nf tc[23:0]
5-36 scsi scripts instruction set saved to system memory and later restored, and scripts can make decisions based on data values in system memory. the scsi first byte received (sfbr) is not writable using the cpu, and therefore not by a memory move. however, it can be loaded using scripts read/write operations. to load the sfbr with a byte stored in system memory, ?rst move the byte to an intermediate SYM53C896 register (for example, a scratch register), and then to the scsi first byte received (sfbr) . the same address alignment restrictions apply to register access operations as to normal memory-to-memory transfers. 5.6.3 second dword figure 5.13 memory move instructions - second dword - dsps register [31:0] these bits contain the source address of the memory move. if the source address is in the 64-bit address space, the bits will be contained in the memory move read selector (mmrs) register. 5.6.4 third dword figure 5.14 memory move instructions - third dword 31 24 23 16 15 8 7 0 dsps register 31 24 23 16 15 8 7 0 mmrs register 31 24 23 16 15 8 7 0 temp register
load/store instructions 5-37 temp register [31:0] these bits contain the destination address for the memory move. if the destination address is in the 64-bit address space, the bits will be contained in the memory move write selec- tor (mmws) register. 5.7 load/store instructions the load/store instructions provide a more ef?cient way to move data from/to memory to/from an internal register in the chip without using the normal memory move instruction. the load/store instructions are represented by two-dword opcodes. the ?rst dword contains the dma command (dcmd) and dma byte counter (dbc) register values. the second dword contains the dma scripts pointer save (dsps) value. this is either the actual memory location of where to load/store, or the offset from the data structure address (dsa) , depending on the value of bit 28 (dsa relative). for load operations where the data is read from the 64-bit address space, the upper dword of address resides in the memory move read selector (mmrs) register. for store operations where the data is written to the 64-bit address space, the upper dword of address resides in the memory move write selector (mmws) register. a maximum of 4 bytes may be moved with these instructions. the register address and memory address must have the same byte alignment, and the count set such that it does not cross dword boundaries. the memory address may not map back to the chip, excluding ram and rom. if it does, a pci read/write cycle occurs (the data does not actually transfer to/from the chip), and the chip issues an interrupt (illegal instruction detected) immediately following. 31 24 23 16 15 8 7 0 mmws register
5-38 scsi scripts instruction set the siom and diom bits in the dma mode (dmode) register determine whether the destination or source address of the instruction is in memory space or i/o space, as illustrated in the following table. the load/store utilizes the pci commands for i/o read and i/o write to access the i/o space. 5.7.1 first dword figure 5.15 load/store instruction - first dword it[2:0] instruction type [31:29] these bits should be 0b111, indicating the load/store instruction. dsa dsa relative 28 when this bit is cleared, the value in the dma scripts pointer save (dsps) is the actual 32-bit memory address used to perform the load/store to/from. when this bit is set, the chip determines the memory address to perform the load/store to/from by adding the 24 bit signed offset value in the dma scripts pointer save (dsps) to the data structure address (dsa) . bits a1, a0 number of bytes allowed to load/store 00 one, two, three or four 01 one, two, or three 10 one or two 11 one bit source destination siom (load) memory register diom (store) register memory 31 29 28 27 26 25 24 23 16 15 3 2 0 dcmd register dbc register it[2:0] dsa rnfls a[7:0] r bc
load/store instructions 5-39 r reserved [27:26] nf no flush (store instruction only) 25 when this bit is set, the SYM53C896 performs a store without ?ushing the prefetch unit. when this bit is cleared, the store instruction automatically ?ushes the prefetch unit. use no flush if the source and destination are not within four instructions of the current store instruction. this bit has no effect on the load instruction. note: this bit has no effect unless the prefetch enable bit in the dma control (dcntl) register is set. for information on scripts instruction prefetching, see chapter 2, "functional description" . ls load/store 24 when this bit is set, the instruction is a load. when cleared, it is a store. a[7:0] register address [23:16] a[7:0] selects the register to load/store to/from within the SYM53C896. r reserved [15:3] bc byte count [2:0] this value is the number of bytes to load/store. 5.7.2 second dword figure 5.16 load/store instructions - second dword memory i/o address / dsa offset [31:0] this is the actual memory location of where to load/store, or the offset from the data structure address (dsa) register value. 31 24 23 16 15 8 7 0 dsps register - memory i/o address/dsa offset 31 24 23 16 15 8 7 0 mmrs/mmws register
5-40 scsi scripts instruction set
symbios SYM53C896 pci to dual channel ultra2 scsi multifunction controller 6-1 chapter 6 speci?cations this chapter speci?es the SYM53C896 electrical and mechanical characteristics. it is divided into the following sections: section 6.1, dc characteristics section 6.2, tolerant technology electrical characteristics section 6.3, ac characteristics section 6.4, pci and external memory interface timing diagrams section 6.5, scsi timing diagrams 6.1 dc characteristics table 6.1 absolute maximum stress ratings symbol parameter min max 1 1. stresses beyond those listed above may cause permanent damage to the device. these are stress ratings only; functional operation of the device at these or any other conditions beyond those indicated in the operating conditions section of the manual is not implied. unit test conditions t stg storage temperature - 55 150 cC v dd supply voltage - 0.5 4.5 v C v in input voltage v ss - 0.3 v dd +0.3 v C i lp 2 2. - 2v 6-2 speci?cations note: v cm = 0.7C1.8 v (common mode, nominal ~1.2 v), r l = 0C110 w, r bias = 9.76 k w. figure 6.1 lvd driver table 6.2 operating conditions symbol parameter min max 1 1. conditions that exceed the operating limits may cause the device to function incorrectly. 2. core and analog supply only. unit test conditions v dd supply voltage 3.13 3.47 v C i dd supply current (dynamic) 2 C 200 ma C i dd-i/o lvd mode supply current (dynamic) C 600 ma rbias = 9.76 k w v dd = 3.3 v i dd supply current (static) C 1 ma C t a operating free air 0 70 cC q ja thermal resistance (junction to ambient air) C 20 c/w C table 6.3 lvd driver scsi signalssd[15:0], sdp[1:0], sreq/, sreq2/, sack/, sack2/, smsg/, sio/, scd/, satn/, sbsy/, ssel/, srst/ symbol parameter min max units test conditions i o + source (+) current - 7 - 13 ma asserted state i o - sink ( - ) current 7 13 ma asserted state i o + source (+) current 3.5 6.5 ma negated state i o - sink ( - ) current - 3.5 - 6.5 ma negated state i oz 3-state leakage - 20 20 m a0,v dd = 3 max r l 2 v cm + i o + r l 2 i o - -
dc characteristics 6-3 note: v cm = 0.7C1.8 v (common mode voltage, nominal ~1.2 v). figure 6.2 lvd receiver table 6.4 lvd receiver scsi signalssd[15:0], sdp[1:0], sreq/, sreq2/, sack/, sack2/, smsg/, sio/, scd/, satn/, sbsy/, ssel/, srst/ symbol parameter min max units test condition v i lvd receiver voltage asserting 120 C mv ac test v i lvd receiver voltage negating C - 120 mv at speed v cm + - + + + - - - v i 2 v i 2 table 6.5 a and b diffsens scsi signals symbol parameter min max unit test conditions v ih hvd sense voltage 2.4 5.0 v note 1 v s lvd sense voltage 0.7 1.9 v note 1 v il se sense voltage v ss - 0.3 0.5 v note 1 i oz 3-state leakage - 10 10 m a0v dd = 3 max 1. functional test speci?ed v ih /v il for each mode. table 6.6 input capacitance symbol parameter min max unit test conditions c i input capacitance of input pads C 7 pf guaranteed by design c io input capacitance of i/o pads C 15 pf guaranteed by design
6-4 speci?cations table 6.7 bidirectional signalsgpio0_fetch/, gpio1_master/, gpio2, gpio3, gpio4, mad[7:0] 1 symbol parameter min max unit test conditions v ih input high voltage 2.0 5.0 v C v il input low voltage v ss - 0.5 0.8 v C v oh output high voltage 2.4 v dd Cv - 8 ma dynamic v ol output low voltage v ss 0.4 v 8 ma dynamic i oz 3-state leakage - 10 10 m a 0, 5.25 v i pull pull down current +7.5 +75 m aC 1. for channels a and b (except mad[7:0]). table 6.8 output signalsmas/[1:0], mce/, moe/_testout 1 , mwe/, tdo symbol parameter min max unit test conditions v oh output high voltage 2.4 v dd Cv - 4 ma dynamic v ol output low voltage v ss 0.4 v 4 ma dynamic i oz 3-state leakage - 10 10 m a 0, 5.25 v 1. moe/_testout is not tested for 3-state leakage. it cannot be 3-stated.
dc characteristics 6-5 table 6.9 bidirectional signalsad[63:0], c_be[7:0]/, frame/, irdy/, trdy/, devsel/, stop/, perr/, par, par64, req64/, ack64/ symbol parameters min max unit test conditions v ih input high voltage 0.5 v dd max 5.0 v v dd 3 max v il input low voltage - 0.5 0.3 v dd min vv dd 3 min v oh output high voltage 0.9 v dd min Cv - 500 m a v ol output low voltage C 0.1 v dd min v 1500 m a v oh 5 v tolerant output high voltage 2.4 C v - 2ma v ol 5 v tolerant output low voltage C 0.55 v 6 ma i oz 3-state leakage - 10 10 m a 0, 5.25 v i pull-down pull down current 1 7.5 75 m aC 1. pull-down text does not apply to ad[31:0] and c_be[3:0]/. table 6.10 input signalsclk, gnt/, idsel, int_dir, rst/, sclk, tck, tdi, test_hsc, test_rst/, tms symbol parameters min max unit test conditions v ih input high voltage 0.5 v dd 5.0 v v dd 1 max 1. 3-state leakage low does not apply to test_rst/. pull-up spec does not apply to: sclk, clk, gnt/, idsel, and rst/. test_hsc has a pull-down. v il input low voltage - 0.5 0.3 v dd vv dd 1 max i in 3-state leakage - 10 10 m a 0, 5.25 v i pull-up pull up current - only on int_dir - 75 - 7.5 m aC
6-6 speci?cations table 6.11 output signalsinta, intb, alt_inta, alt_intb, req/ symbol parameters min max unit test conditions v oh output high voltage 0.9 v dd Cv - 500 m a v ol output low voltage C 0.1 v dd v 1500 m a v oh 5 v tolerant output high voltage 2.4 C v - 2ma v ol 5 v tolerant output low voltage C 0.55 v 6 ma i oz 3-state leakage - 10 10 m a 0, 5.25 v i pull-up pull-up current 1 - 75 - 7.5 m aC 1. pull-up test does not apply to req/. table 6.12 output signalserr/ symbol parameters min max unit test conditions v ol output low voltage C 0.1 v dd v 1.5 ma i oz 3-state leakage - 10 10 m aC
tolerant technology electrical characteristics 6-7 6.2 tolerant technology electrical characteristics table 6.13 tolerant technology electrical characteristics for se scsi signals 1 symbol parameter min max units test conditions v oh 2 output high voltage 2.0 v dd +0.3 v i oh =7ma v ol output low voltage v ss 0.5 v i ol =48ma v ih input high voltage 2.0 v dd +0.3 v C v il input low voltage v ss - 0.3 0.8 v referenced to v ss v ik input clamp voltage - 0.66 - 0.77 v v dd = 4.75; i i = - 20 ma v th threshold, high to low 1.0 1.2 v C v tl threshold, low to high 1.4 1.6 v C v th -v tl hysteresis 300 500 mv C i oh 2 output high current 2.5 24 ma v oh = 2.5 v i ol output low current 100 200 ma v ol = 0.5 v i osh 2 short-circuit output high current C 625 ma output driving low, pin shorted to v dd supply 3 i osl short-circuit output low current C 95 ma output driving high, pin shorted to v ss supply i lh input high leakage C 20 m a - 0.5 6-8 speci?cations figure 6.3 rise and fall time test condition figure 6.4 scsi input filtering esd electrostatic discharge 2 C kv mil-std-883c; 3015-7 latch-up 100 C ma C filter delay 20 30 ns figure 6.4 ultra ?lter delay 10 15 ns figure 6.4 ultra2 ?lter delay 5 8 ns figure 6.4 extended ?lter delay 40 60 ns figure 6.4 1. these values are guaranteed by periodic characterization; they are not 100% tested on every device. 2. active negation outputs only: data, parity, sreq/, sack/. (minus pins) scsi mode only. 3. single pin only; irreversible damage may occur if sustained for one second. 4. scsi reset pin has 10 k w pull-up resistor. table 6.13 tolerant technology electrical characteristics for se scsi signals 1 symbol parameter min max units test conditions + - 2.5 v 47 w 20 pf req/ or ack/ input t 1 v th note: t 1 is the input ?ltering period.
tolerant technology electrical characteristics 6-9 figure 6.5 hysteresis of scsi receivers figure 6.6 input current as a function of input voltage 1 0 received logic level input voltage (volts) 1.1 1.3 1.5 1.7 +40 +20 0 -20 -40 -4 0 4 8 12 16 -0.7 v 8.2 v hi-z output active input voltage (volts) input current (milliamperes) 14.4 v
6-10 speci?cations figure 6.7 output current as a function of output voltage output sink current (milliamperes) 0 -200 -400 -600 -800 012345 output voltage (volts) output source current (milliamperes) output voltage (volts) 0123 45 100 80 60 40 20 0
ac characteristics 6-11 6.3 ac characteristics the ac characteristics described in this section apply over the entire range of operating conditions (refer to section 6.1, dc characteristics ). chip timing is based on simulation at worst case voltage, temperature, and processing. timing was developed with a load capacitance of 50 pf. figure 6.8 external clock table 6.14 external clock 1 1. timing is for an external 40 mhz clock. a quadrupled 40 mhz clock is required for ultra2 scsi operation. symbol parameter min max units t 1 bus clock cycle time 30 dc ns scsi clock cycle time (sclk) 2 2. this parameter must be met to ensure scsi timing is within speci?cation. 25 60 ns t 2 clk low time 3 3. duty cycle not to exceed 60/40. 10 C ns sclk low time 3 633ns t 3 clk high time 3 12 C ns sclk high time 3 10 33 ns t 4 clk slew rate 1 C v/ns sclk slew rate 1 C v/ns clk, sclk 1.4 v t 1 t 3 t 4 t 2
6-12 speci?cations figure 6.9 reset input figure 6.10 interrupt output table 6.15 reset input symbol parameter min max units t 1 reset pulse width 10 C t clk t 2 reset deasserted setup to clk high 0 C ns t 3 mad setup time to clk high (for con?guring the mad bus only) 20 C ns t 4 mad hold time from clk high (for con?guring the mad bus only) 20 C ns t 1 t 2 t 3 t 4 clk rst/ mad* *when enabled valid data table 6.16 interrupt output symbol parameter min max units t 1 clk high to irq/ low 2 11 ns t 2 clk high to irq/ high 2 11 ns t 3 irq/ deassertion time 3 C clk t 1 t 2 t 3 irq/ clk
pci and external memory interface timing diagrams 6-13 6.4 pci and external memory interface timing diagrams figure 6.11 through figure 6.34 represent signal activity when the SYM53C896 accesses the pci bus. this section includes timing diagrams for access to three groups of memory con?gurations. the ?rst group applies to target timing . the second group applies to i initiator timing . the third group applies to external memory timing . note: multiple byte accesses to the external memory bus increase the read or write cycle by 11 clocks for each additional byte. timing diagrams included in this section are: target timing C pci con?guration register read C pci con?guration register write C operating register/scripts ram read, 32 and 64-bit C operating register/scripts ram write, 32 and 64-bit initiator timing C nonburst opcode fetch, 32-bit address and data C burst opcode fetch, 32-bit address and data C back to back read, 32-bit address and data C back to back write, 32-bit address and data C burst read, 32 and 64-bit C burst write, 32 and 64-bit external memory timing C external memory read C external memory write C normal/fast memory ( 3 128 kbytes) single byte access read cycle C normal/fast memory ( 3 128 kbytes) single byte access write cycle
6-14 speci?cations C normal/fast memory ( 3 128 kbytes) multiple byte access read cycle C normal/fast memory ( 3 128 kbytes) multiple byte access write cycle C slow memory ( 3 128 kbytes) read cycle C slow memory ( 3 128 kbytes) write cycle C 64 kbytes rom read cycle C 64 kbytes rom write cycle
pci and external memory interface timing diagrams 6-15 6.4.1 target timing figure 6.11 pci con?guration register read table 6.17 pci con?guration register read symbol parameter min max unit t 1 shared signal input setup time 7 C ns t 2 shared signal input hold time 0 C ns t 3 clk to shared signal output valid C 11 ns data out byte enable addr in t 2 in out t 1 t 2 t 1 t 3 t 2 t 1 t 1 t 2 t 2 t 3 t 3 t 2 t 1 t 3 t 2 t 1 clk (driven by system) frame/ (driven by system) ad[31:0] (driven by master-addr; SYM53C896-data) c_be[3:0]/ (driven by master) pa r (driven by master-addr; SYM53C896-data) irdy/ (driven by master) trdy/ (driven by SYM53C896) stop/ (driven by SYM53C896) devsel/ (driven by SYM53C896) idsel (driven by master) cmd
6-16 speci?cations figure 6.12 pci con?guration register write table 6.18 pci con?guration register write symbol parameter min max unit t 1 shared signal input setup time 7 C ns t 2 shared signal input hold time 0 C ns t 3 clk to shared signal output valid C 11 ns data in byte enable addr in t 2 t 1 t 2 t 1 t 2 t 1 t 1 t 2 t 2 t 3 t 2 t 1 t 3 t 2 t 1 clk (driven by system) frame/ (driven by master) ad[31:0] (driven by master) c_be[3:0]/ (driven by master) pa r (driven by master) irdy/ (driven by master) trdy/ (driven by SYM53C896) stop/ (driven by SYM53C896) devsel/ (driven by SYM53C896) idsel (driven by master) t 1 t 2 cmd
pci and external memory interface timing diagrams 6-17 figure 6.13 operating registers/scripts ram read, 32-bit table 6.19 operating register/scripts ram read, 32-bit symbol parameter min max unit t 1 shared signal input setup time 7 C ns t 2 shared signal input hold time 0 C ns t 3 clk to shared signal output valid C 11 ns data byte enable addr in t 2 t 1 t 2 t 1 t 2 t 1 t 1 t 2 t 2 t 3 t 2 t 1 t 3 clk (driven by system) frame/ (driven by master) ad[31:0] (driven by master-addr; c_be[3:0]/ (driven by master) pa r (driven by master-addr; irdy/ (driven by master) trdy/ (driven by SYM53C896) stop/ (driven by SYM53C896) devsel/ (driven by SYM53C896) out t 3 in out t 3 SYM53C896-data) SYM53C896-data cmd
6-18 speci?cations figure 6.14 operating register/scripts ram read, 64-bit table 6.20 operating register/scripts ram read, 64-bit symbol parameter min max unit t 1 shared signal input setup time 7 C ns t 2 shared signal input hold time 0 C ns t 3 clk to shared signal output valid C 11 ns data byte enable t 2 t 1 t 2 t 1 t 2 t 2 t 2 t 3 t 2 t 1 t 3 clk (driven by system) frame/ (driven by master) ad[31:0] (driven by master-addr; c_be[3:0]/ (driven by master) par; par64 (driven by master-addr; irdy/ (driven by master) trdy/ (driven by SYM53C896) stop/ (driven by SYM53C896) devsel/ (driven by SYM53C896) out t 3 in out t 3 SYM53C896-data) SYM53C896-data t 1 t 2 addr lo addr hi t 1 dual addr t 1 ad[63:32] (driven by master-addr; SYM53C896-data) hi addr t 2 byte enable t 2 c_be[7:4]/ (driven by master) t 1 bus cmd t 1 t 1 t 2 bus cmd in t 3 req64/ (driven by master) ack64/ (driven by SYM53C896) t 1
pci and external memory interface timing diagrams 6-19 figure 6.15 operating register/scripts ram write, 32-bit table 6.21 operating register/scripts ram write, 32-bit symbol parameter min max unit t 1 shared signal input setup time 7 C ns t 2 shared signal input hold time 0 C ns t 3 clk to shared signal output valid C 11 ns byte enable addr in cmd t 2 t 1 t 2 t 1 t 2 t 1 t 1 t 2 t 2 t 3 t 2 t 1 t 3 clk (driven by system) frame/ (driven by master) ad[31:0] (driven by master) c_be[3:0]/ (driven by master) pa r (driven by master) irdy/ (driven by master) trdy/ (driven by SYM53C896) stop/ (driven by SYM53C896) devsel/ (driven by SYM53C896) in t 2 data in t 1 in t 2 t 1
6-20 speci?cations table 6.22 operating register/scripts ram write, 64-bit symbol parameter min max unit t 1 shared signal input setup time 7 C ns t 2 shared signal input hold time 0 C ns t 3 clk to shared signal output valid C 11 ns
pci and external memory interface timing diagrams 6-21 figure 6.16 operating register/scripts ram write, 64-bit byte enable t 2 t 1 t 2 t 1 t 2 t 1 t 2 t 2 t 3 t 2 t 1 t 3 clk (driven by system) frame/ (driven by master) ad[31:0] (driven by master) c_be[3:0]/ (driven by master) par; par64 (driven by master) irdy/ (driven by master) trdy/ (driven by SYM53C896) stop/ (driven by SYM53C896) devsel/ (driven by SYM53C896) in in t 1 t 2 addr lo addr hi t 1 dual addr t 1 ad[63:32] (driven by master) hi addr byte enable t 2 c_be[7:4]/ (driven by master) t 1 bus cmd t 1 t 2 bus cmd in req64/ (driven by master) ack64/ (driven by SYM53C896) data in t 2 data in t 1 t 2 t 1
6-22 speci?cations 6.4.2 initiator timing table 6.23 nonburst opcode fetch, 32-bit address and data symbol parameter min max unit t 1 shared signal input setup time 7 C ns t 2 shared signal input hold time 0 C ns t 3 clk to shared signal output valid 2 11 ns t 4 side signal input setup time 10 C ns t 5 side signal input hold time 0 C ns t 6 clk to side signal output valid C 12 ns t 7 clk high to gpio0_fetch/ low C 20 ns t 8 clk high to gpio0_fetch/ high C 20 ns t 9 clk high to gpio1_master/ low C 20 ns t 10 clk high to gpio1_master/ high C 20 ns
pci and external memory interface timing diagrams 6-23 figure 6.17 nonburst opcode fetch, 32-bit address and data t 7 t 9 t 3 t 4 t 1 t 3 t 1 clk (driven by system) gpio0_fetch/ (driven by SYM53C896) gpio1_master/ (driven by SYM53C896) req/ (driven by SYM53C896) pa r (driven by SYM53C896- irdy/ (driven by SYM53C896) trdy/ (driven by target) stop/ (driven by target) devsel/ (driven by target) t 1 t 8 t 6 t 3 ad[31:0] (driven by SYM53C896- c_be[3:0]/ (driven by SYM53C896) t 3 cmd t 2 req64/ (driven by SYM53C896) ack64/ (driven by SYM53C896) t 10 t 1 t 2 gnt/ (driven by arbiter) frame/ (driven by SYM53C896) t 5 data in addr out data in addr out byte enable cmd byte enable t 3 t 2 t 2 addr; target-data) addr; target-data)
6-24 speci?cations table 6.24 burst opcode fetch, 32-bit address and data symbol parameter min max unit t 1 shared signal input setup time 7 C ns t 2 shared signal input hold time 0 C ns t 3 clk to shared signal output valid 2 11 ns t 4 side signal input setup time 10 C ns t 5 side signal input hold time 0 C ns t 6 clk to side signal output valid C 12 ns t 7 clk high to gpio0_fetch/ low C 20 ns t 8 clk high to gpio0_fetch/ high C 20 ns t 9 clk high to gpio1_master/ low C 20 ns t 10 clk high to gpio1_master/ high C 20 ns
pci and external memory interface timing diagrams 6-25 figure 6.18 burst opcode fetch, 32-bit address and data t 7 t 9 t 3 t 4 t 1 t 3 t 1 clk (driven by system) gpio0_fetch/ (driven by SYM53C896) gpio1_master/ (driven by SYM53C896) req/ (driven by SYM53C896) pa r (driven by SYM53C896- irdy/ (driven by SYM53C896) trdy/ (driven by target) stop/ (driven by target) devsel/ (driven by target) t 1 t 8 t 6 t 3 ad[31:0] (driven by SYM53C896- c_be[3:0]/ (driven by SYM53C896) t 3 cmd req64/ (driven by SYM53C896) ack64/ (driven by SYM53C896) t 10 t 1 t 2 gnt/ (driven by arbiter) frame/ (driven by SYM53C896) data in data in byte enable t 3 t 2 t 2 addr; target-data) addr; target-data) addr out out in in t 5 t 3 t 2
6-26 speci?cations table 6.25 back-to-back read, 32-bit address and data symbol parameter min max unit t 1 shared signal input setup time 7 C ns t 2 shared signal input hold time 0 C ns t 3 clk to shared signal output valid 2 11 ns t 4 side signal input setup time 10 C ns t 5 side signal input hold time 0 C ns t 6 clk to side signal output valid C 12 ns t 9 clk high to gpio1_master/ low C 20 ns t 10 clk high to gpio1_master/ high C 20 ns
pci and external memory interface timing diagrams 6-27 figure 6.19 back-to-back read, 32-bit address and data t 9 t 4 t 1 t 3 t 1 clk (driven by system) gpio0_fetch/ (driven by SYM53C896) gpio1_master/ (driven by SYM53C896) req/ (driven by SYM53C896) pa r (driven by SYM53C896- irdy/ (driven by SYM53C896) trdy/ (driven by target) stop/ (driven by target) devsel/ (driven by target) t 1 t 6 t 3 ad[31:0] (driven by SYM53C896- c_be[3:0]/ (driven by SYM53C896) t 3 t 2 req64/ (driven by SYM53C896) ack64/ (driven by SYM53C896) t 10 t 1 t 2 gnt/ (driven by arbiter) frame/ (driven by SYM53C896) t 5 data in addr out data in addr out cmd t 3 t 2 t 2 addr; target-data) addr; target-data) t 3 be be out in out in cmd
6-28 speci?cations table 6.26 back-to-back write, 32-bit address and data symbol parameter min max unit t 1 shared signal input setup time 7 C ns t 2 shared signal input hold time 0 C ns t 3 clk to shared signal output valid 2 11 ns t 4 side signal input setup time 10 C ns t 5 side signal input hold time 0 C ns t 6 clk to side signal output valid C 12 ns t 9 clk high to gpio1_master/ low C 20 ns t 10 clk high to gpio1_master/ high C 20 ns
pci and external memory interface timing diagrams 6-29 figure 6.20 back-to-back write, 32-bit address and data t 9 t 4 t 1 t 3 t 1 clk (driven by system) gpio0_fetch/ (driven by SYM53C896) gpio1_master/ (driven by SYM53C896) req/ (driven by SYM53C896) pa r (driven by SYM53C896- irdy/ (driven by SYM53C896) trdy/ (driven by target) stop/ (driven by target) devsel/ (driven by target) t 6 t 3 ad[31:0] (driven by SYM53C896- c_be[3:0]/ (driven by SYM53C896) t 3 cmd t 2 req64/ (driven by SYM53C896) ack64/ (driven by SYM53C896) t 10 t 1 gnt/ (driven by arbiter) frame/ (driven by SYM53C896) t 5 addr out addr out cmd t 3 t 2 t 2 addr; target-data) addr; target-data) t 3 be be data out data out t 3 t 3 t 3
6-30 speci?cations table 6.27 burst read, 32-bit address and data symbol parameter min max unit t 1 shared signal input setup time 7 C ns t 2 shared signal input hold time 0 C ns t 3 clk to shared signal output valid 2 11 ns
pci and external memory interface timing diagrams 6-31 figure 6.21 burst read, 32-bit address and data t 1 t 2 clk (driven by system) gpio0_fetch/ (driven by SYM53C896) gpio1_master/ (driven by SYM53C896) req/ (driven by SYM53C896) pa r (driven by SYM53C896- irdy/ (driven by SYM53C896) trdy/ (driven by target) stop/ (driven by target) devsel/ (driven by target) ad[31:0] (driven by SYM53C896- c_be[3:0]/ (driven by SYM53C896) t 3 cmd gnt/ (driven by arbiter) frame/ (driven by SYM53C896) addr out t 2 addr; target-data) addr; target-data) data in out in in be
6-32 speci?cations table 6.28 burst read, 64-bit address and data symbol parameter min max unit t 1 shared signal input setup time 7 C ns t 2 shared signal input hold time 0 C ns t 3 clk to shared signal output valid 2 11 ns t 10 clk high to gpio1_master/ high C 20 ns
pci and external memory interface timing diagrams 6-33 figure 6.22 burst read, 64-bit address and data t 1 t 2 clk (driven by system) gpio0_fetch/ (driven by SYM53C896) gpio1_master/ (driven by SYM53C896) req/ (driven by SYM53C896) par; par64 (addr drvn by 896;- irdy/ (driven by SYM53C896) trdy/ (driven by target) stop/ (driven by target) devsel/ (driven by target) ad[31:0] (driven by SYM53C896- c_be[3:0]/ (driven by SYM53C896) t 3 gnt/ (driven by arbiter) frame/ (driven by SYM53C896) addr out lo t 2 t 2 addr; target-data) data drvn by target) t 1 data in in out in in req64/ (driven by SYM53C896) ack64/ (driven by target) addr out hi t 2 t 10 bus dual addr cmd ad[63:32] (driven by SYM53C896- c_be[7:4]/ (driven by SYM53C896) addr; target-data) be data in hi address bus cmd be
6-34 speci?cations table 6.29 burst write, 32-bit address and data symbol parameter min max unit t 1 shared signal input setup time 7 C ns t 2 shared signal input hold time 0 C ns t 3 clk to shared signal output valid 2 11 ns t 10 clk high to gpio1_master/ high C 20 ns
pci and external memory interface timing diagrams 6-35 figure 6.23 burst write, 32-bit address and data t 1 clk (driven by system) gpio0_fetch/ (driven by SYM53C896) gpio1_master/ (driven by SYM53C896) req/ (driven by SYM53C896) pa r (driven by SYM53C896) irdy/ (driven by SYM53C896) trdy/ (driven by target) stop/ (driven by target) devsel/ (driven by target) ad[31:0] (driven by SYM53C896) c_be[3:0]/ (driven by SYM53C896) t 3 cmd gnt/ (driven by arbiter) frame/ (driven by SYM53C896) addr out t 2 be data out data out t 10 t 1 t 2
6-36 speci?cations table 6.30 burst write, 64-bit address and data symbol parameter min max unit t 1 shared signal input setup time 7 C ns t 2 shared signal input hold time 0 C ns t 3 clk to shared signal output valid 2 11 ns t 10 clk high to gpio1_master/ high C 20 ns
pci and external memory interface timing diagrams 6-37 figure 6.24 burst write, 64-bit address and data t 1 clk (driven by system) gpio0_fetch/ (driven by SYM53C896) gpio1_master/ (driven by SYM53C896) req/ (driven by SYM53C896) par; par64 (driven by SYM53C896) irdy/ (driven by SYM53C896) trdy/ (driven by target) stop/ (driven by target) devsel/ (driven by target) ad[31:0] (driven by SYM53C896) c_be[3:0]/ (driven by SYM53C896) t 3 gnt/ (driven by arbiter) frame/ (driven by SYM53C896) addr out lo t 2 t 2 req64/ (driven by SYM53C896) ack64/ (driven by target) addr out hi t 2 t 10 bus dual addr cmd ad[63:32] (driven by SYM53C896) c_be[7:4]/ (driven by SYM53C896) hi address bus cmd t 1 data out data out be be data out data out be be t 3 t 1 t 2
6-38 speci?cations 6.4.3 external memory timing table 6.31 external memory read symbol parameter min max unit t 1 shared signal input setup time 7 C ns t 2 shared signal input hold time 0 C ns t 3 clk to shared signal output valid C 11 ns t 11 address setup to mas/ high 25 C ns t 12 address hold from mas/ high 15 C ns t 13 mas/ pulse width 25 C ns t 14 mce/ low to data clocked in 160 C ns t 15 address valid to data clocked in 205 C ns t 16 moe/ low to data clocked in 100 C ns t 17 data hold from address, moe/, mce/ change 0 C ns t 19 data setup to clk high 5 C ns
pci and external memory interface timing diagrams 6-39 figure 6.25 external memory read clk (driven by system) pa r (driven by master-addr; irdy/ (driven by master) trdy/ (driven by SYM53C896) stop/ (driven by SYM53C896) devsel/ (driven by SYM53C896) ad[31:0] (driven by master-addr; c_be[3:0]/ (driven by master) frame/ (driven by master) data driven by memory) 1234 56 78910 SYM53C896-data) addr in byte enable SYM53C896-data) mad (addr drvn by SYM53C896 ; high order address middle order address low order address mas1/ (driven by SYM53C896) mas0/ (driven by SYM53C896) mce/ (driven by SYM53C896) moe/ (driven by SYM53C896) mwe/ (driven by SYM53C896) t 1 t 2 t 1 t 2 cmd in t 1 t 2 t 1 t 2 t 1 t 3 t 13 t 11 t 12 t 15
6-40 speci?cations figure 6.25 external memory read (cont.) clk (driven by system) pa r (driven by master-addr; irdy/ (driven by master) trdy/ (driven by SYM53C896) stop/ (driven by SYM53C896) devsel/ (driven by SYM53C896) ad[31:0] (driven by master-addr; c_be[3:0]/ (driven by master) frame/ (driven by master) data driven by memory) 11 12 13 14 15 16 17 18 19 20 SYM53C896-data) data out SYM53C896-data) mad (addr drvn by SYM53C896; mas1/ (driven by SYM53C896) mas0/ (driven by SYM53C896) mce/ (driven by SYM53C896) moe/ (driven by SYM53C896) mwe/ (driven by SYM53C896) t 3 t 2 t 2 t 15 21 t 3 out t 3 t 3 data in t 19 t 17 t 14 t 16
pci and external memory interface timing diagrams 6-41 table 6.32 external memory write symbol parameter min max unit t 1 shared signal input setup time 7 C ns t 2 shared signal input hold time 0 C ns t 3 clk to shared signal output valid C 11 ns t 11 address setup to mas/ high 25 C ns t 12 address hold from mas/ high 15 C ns t 13 mas/ pulse width 25 C ns t 20 data setup to mwe/ low 30 C ns t 21 data hold from mwe/ high 20 C ns t 22 mwe/ pulse width 100 C ns t 23 address setup to mwe/ low 75 C ns t 24 mce/ low to mwe/ high 120 C ns t 25 mce/ low to mwe/ low 25 C ns t 26 mwe/ high to mce/ high 25 C ns
6-42 speci?cations figure 6.26 external memory write clk (driven by system) pa r (driven by master-addr; irdy/ (driven by master) trdy/ (driven by SYM53C896) stop/ (driven by SYM53C896) devsel/ (driven by SYM53C896) ad[31:0] (driven by master-addr; c_be[3:0]/ (driven by master) frame/ (driven by master) 12 3 4 5 6 78 910 SYM53C896-data) byte enable SYM53C896-data) mad (driven by SYM53C896) high order address middle order address low order address mas1/ (driven by SYM53C896) mas0/ (driven by SYM53C896) mce/ (driven by SYM53C896) moe/ (driven by SYM53C896) mwe/ (driven by SYM53C896) t 1 t 2 t 1 t 2 cmd in t 1 t 2 t 1 t 2 t 1 t 3 t 13 t 11 t 12 data in t 23 t 20 t 1 addr in
pci and external memory interface timing diagrams 6-43 figure 6.26 external memory write (cont.) clk (driven by system) pa r (driven by master-addr; irdy/ (driven by master) trdy/ (driven by SYM53C896) stop/ (driven by SYM53C896) devsel/ (driven by SYM53C896) ad[31:0] (driven by master-addr; c_be[3:0]/ (driven by master) frame/ (driven by master) 11 12 13 14 15 16 17 18 19 20 SYM53C896-data) SYM53C896-data) mad (driven by SYM53C896) mas1/ (driven by SYM53C896) mas0/ (driven by SYM53C896) mce/ (driven by SYM53C896) moe/ (driven by SYM53C896) mwe/ (driven by SYM53C896) t 2 t 2 t 2 21 t 1 t 3 t 3 t 24 t 22 data in byte enable in data out t 25 t 26 t 21 t 20 t 23 t 2
6-44 speci?cations figure 6.27 normal/fast memory ( 3 128 kbytes) single byte access read cycle table 6.33 normal/fast memory ( 3 128 kbytes) single byte access read cycle symbol parameter min max unit t 11 address setup to mas/ high 25 C ns t 12 address hold from mas/ high 15 C ns t 13 mas/ pulse width 25 C ns t 14 mce/ low to data clocked in 160 C ns t 15 address valid to data clocked in 205 C ns t 16 moe/ low to data clocked in 100 C ns t 17 data hold from address, moe/, mce/ change 0 C ns t 18 address out from moe/, mce/ high 50 C ns t 19 data setup to clk high 5 C ns clk (driven by system) data driven by memory) 12 3 4 5 6 78 910 mad (addr driven by SYM53C896; high order address middle order address low order address mas1/ (driven by SYM53C896) mas0/ (driven by SYM53C896) mce/ (driven by SYM53C896) moe/ (driven by SYM53C896) mwe/ (driven by SYM53C896) t 13 t 11 t 12 t 15 t 14 t 16
pci and external memory interface timing diagrams 6-45 figure 6.27 normal/fast memory ( 3 128 kbytes) single byte access read cycle (cont.) clk (driven by system) data driven by memory) 11 12 13 14 15 16 17 18 19 20 mad (addr driven by SYM53C896; mas1/ (driven by SYM53C896) mas0/ (driven by SYM53C896) mce/ (driven by SYM53C896) moe/ (driven by SYM53C896) mwe/ (driven by SYM53C896) t 15 21 read data t 19 t 17 t 14 t 16 valid t 18
6-46 speci?cations figure 6.28 normal/fast memory ( 3 128 kbytes) single byte access write cycle table 6.34 normal/fast memory ( 3 128 kbytes) single byte access write cycle symbol parameter min max unit t 11 address setup to mas/ high 25 C ns t 12 address hold from mas/ high 15 C ns t 13 mas/ pulse width 25 C ns t 20 data setup to mwe/ low 30 C ns t 21 data hold from mwe/ high 20 C ns t 22 mwe/ pulse width 100 C ns t 23 address setup to mwe/ low 75 C ns t 24 mce/ low to mwe/ high 120 C ns t 25 mce/ low to mwe/ low 25 C ns t 26 mwe/ high to mce/ high 25 C ns clk (driven by system) 12 3 4 5 6 78 910 mad (driven by SYM53C896) high order address middle order address low order address mas1/ (driven by SYM53C896) mas0/ (driven by SYM53C896) mce/ (driven by SYM53C896) moe/ (driven by SYM53C896) mwe/ (driven by SYM53C896) t 13 t 11 t 12 t 24 t 25 write data valid t 23 t 20
pci and external memory interface timing diagrams 6-47 figure 6.28 normal/fast memory ( 3 128 kbytes) single byte access write cycle (cont.) clk (driven by system) 11 12 13 14 15 16 17 18 19 20 mad (driven by SYM53C896) mas1/ (driven by SYM53C896) mas0/ (driven by SYM53C896) mce/ (driven by SYM53C896) moe/ (driven by SYM53C896) mwe/ (driven by SYM53C896) 21 t 24 t 25 t 21 valid write data t 20 t 23 t 22 t 26
6-48 speci?cations figure 6.29 normal/fast memory ( 3 128 kbytes) multiple byte access read cycle clk (driven by system) pa r (driven by SYM53C896- irdy/ (driven by master) trdy/ (driven by SYM53C896) stop/ (driven by SYM53C896) devsel/ (driven by SYM53C896) ad[31:0] (driven by SYM53C896- c_be[3:0]/ (driven by master) frame/ (driven by master) master-addr; data) master-addr;-data) mad (addr driven by SYM53C896 mas1/ (driven by SYM53C896) mas0/ (driven by SYM53C896) mce/ (driven by SYM53C896) moe/ (driven by SYM53C896) mwe/ (driven by SYM53C896) 12 345 6789101112131415 in addr cmd byte enable in data driven by memory) high order address order address middle order address low
pci and external memory interface timing diagrams 6-49 figure 6.29 normal/fast memory ( 3 128 kbytes) multiple byte access read cycle (cont.) clk (driven by system) pa r (driven by SYM53C896- irdy/ (driven by master) trdy/ (driven by SYM53C896) stop/ (driven by SYM53C896) devsel/ (driven by SYM53C896) ad[31:0] (driven by SYM53C896- c_be[3:0]/ (driven by master) frame/ (driven by master) master-addr; data) master-addr;-data) mad (addr driven by SYM53C896 mas1/ (driven by SYM53C896) mas0/ (driven by SYM53C896) mce/ (driven by SYM53C896) moe/ (driven by SYM53C896) mwe/ (driven by SYM53C896) 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 byte enable data driven by memory) 16 32 33 data out out data in low order address data in
6-50 speci?cations figure 6.30 normal/fast memory ( 3 128 kbytes) multiple byte access write cycle clk (driven by system) pa r (driven by master-addr; irdy/ (driven by master) trdy/ (driven by SYM53C896) stop/ (driven by SYM53C896) devsel/ (driven by SYM53C896) ad[31:0] (driven by master-addr; c_be[3:0]/ (driven by master) frame/ (driven by master) SYM53C896-data) SYM53C896-data) mad (driven by SYM53C896) mas1/ (driven by SYM53C896) mas0/ (driven by SYM53C896) mce/ (driven by SYM53C896) moe/ (driven by SYM53C896) mwe/ (driven by SYM53C896) 12 345 6789101112131415 addr cmd in high order address order address middle order address low data out byte enable data in in
pci and external memory interface timing diagrams 6-51 figure 6.30 normal/fast memory ( 3 128 kbytes) multiple byte access write cycle (cont.) clk (driven by system) pa r (driven by master-addr; irdy/ (driven by master) trdy/ (driven by SYM53C896) stop/ (driven by SYM53C896) devsel/ (driven by SYM53C896) ad[31:0] (driven by master-addr; c_be[3:0]/ (driven by master) frame/ (driven by master) SYM53C896-data) SYM53C896-data) mad (driven by SYM53C896 mas1/ (driven by SYM53C896) mas0/ (driven by SYM53C896) mce/ (driven by SYM53C896) moe/ (driven by SYM53C896) mwe/ (driven by SYM53C896) 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 byte enable 16 32 33 low order address data in in data out
6-52 speci?cations figure 6.31 slow memory ( 3 128 kbytes) read cycle table 6.35 slow memory ( 3 128 kbytes) read cycle symbol parameter min max unit t 11 address setup to mas/ high 25 C ns t 12 address hold from mas/ high 15 C ns t 13 mas/ pulse width 25 C ns t 14 mce/ low to data clocked in 160 C ns t 15 address valid to data clocked in 205 C ns t 16 moe/ low to data clocked in 100 C ns t 17 data hold from address, moe/, mce/ change 0 C ns t 18 address out from moe/, mce/ high 50 C ns t 19 data setup to clk high 5 C ns clk (driven by system) 12 3 4 5 6 78 910 mad (addr driven by SYM53C896 high order address middle order address low order address mas1/ (driven by SYM53C896) mas0/ (driven by SYM53C896) mce/ (driven by SYM53C896) moe/ (driven by SYM53C896) mwe/ (driven by SYM53C896) t 13 t 11 t 12 t 15 t 16 data drvn by mem) t 14
pci and external memory interface timing diagrams 6-53 figure 6.31 slow memory ( 3 128 kbytes) read cycle (cont.) clk (driven by system) data driven by memory) 11 12 13 14 15 16 17 18 19 20 mad (addr driven by SYM53C896; mas1/ (driven by SYM53C896) mas0/ (driven by SYM53C896) mce/ (driven by SYM53C896) moe/ (driven by SYM53C896) mwe/ (driven by SYM53C896) t 15 21 read data t 19 t 17 t 14 t 16 valid t 18 22
6-54 speci?cations figure 6.32 slow memory ( 3 128 kbytes) write cycle table 6.36 slow memory ( 3 128 kbytes) write cycle symbol parameter min max unit t 11 address setup to mas/ high 25 C ns t 12 address hold from mas/ high 15 C ns t 13 mas/ pulse width 25 C ns t 20 data setup to mwe/ low 30 C ns t 21 data hold from mwe/ high 20 C ns t 22 mwe/ pulse width 100 C ns t 23 address setup to mwe/ low 75 C ns t 24 mce/ low to mwe/ high 120 C ns t 25 mce/ low to mwe/ low 25 C ns t 26 mwe/ high to mce/ high 25 C ns clk (driven by system) 12 3 4 5 6 78 910 mad (driven by SYM53C896) high order address middle order address low order address mas1/ (driven by SYM53C896) mas0/ (driven by SYM53C896) mce/ (driven by SYM53C896) moe/ (driven by SYM53C896) mwe/ (driven by SYM53C896) t 13 t 11 t 12 t 24 t 25 write data valid t 23 t 20
pci and external memory interface timing diagrams 6-55 figure 6.32 slow memory ( 3 128 kbytes) write cycle (cont.) clk (driven by system) 11 12 13 14 15 16 17 18 19 20 mad (driven by SYM53C896) mas1/ (driven by SYM53C896) mas0/ (driven by SYM53C896) mce/ (driven by SYM53C896) moe/ (driven by SYM53C896) mwe/ (driven by SYM53C896) 21 t 24 t 25 t 21 valid write data t 20 t 23 t 22 t 26
6-56 speci?cations figure 6.33 64 kbytes rom read cycle table 6.37 64 kbytes rom read cycle symbol parameter min max unit t 11 address setup to mas/ high 25 C ns t 12 address hold from mas/ high 15 C ns t 13 mas/ pulse width 25 C ns t 14 mce/ low to data clocked in 160 C ns t 15 address valid to data clocked in 205 C ns t 16 moe/ low to data clocked in 100 C ns t 17 data hold from address, moe/, mce/ change 0 C ns t 18 address out from moe/, mce/ high 50 C ns t 19 data setup to clk high 5 C ns clk (driven by system) 1234 5 6 78910 mad (addr driven by SYM53C896; high order address low order address mas1/ (driven by SYM53C896) mas0/ (driven by SYM53C896) mce/ (driven by SYM53C896) moe/ (driven by SYM53C896) mwe/ (driven by SYM53C896) t 13 t 11 t 12 t 15 t 16 11 12 13 14 15 valid read data t 14 t 18 t 19 t 17 data driven by memory)
pci and external memory interface timing diagrams 6-57 figure 6.34 64 kbytes rom write cycle table 6.38 64 kbytes rom write cycle symbol parameter min max unit t 11 address setup to mas/ high 25 C ns t 12 address hold from mas/ high 15 C ns t 13 mas/ pulse width 25 C ns t 20 data setup to mwe/ low 30 C ns t 21 data hold from mwe/ high 20 C ns t 22 mwe/ pulse width 100 C ns t 23 address setup to mwe/ low 75 C ns t 24 mce/ low to mwe/ high 120 C ns t 25 mce/ low to mwe/ low 25 C ns t 26 mwe/ high to mce/ high 25 C ns clk (driven by system) 1234 5 6 78910 mad (driven by SYM53C896) high order address low order address mas1/ (driven by SYM53C896) mas0/ (driven by SYM53C896) mce/ (driven by SYM53C896) moe/ (driven by SYM53C896) mwe/ (driven by SYM53C896) t 13 t 11 t 12 t 22 11 12 13 t 24 t 21 valid write data t 23 t 25 t 26 t 20
6-58 speci?cations 6.5 scsi timing diagrams figure 6.35 initiator asynchronous send figure 6.36 initiator asynchronous receive table 6.39 initiator asynchronous send symbol parameter min max units t 1 sack/ asserted from sreq/ asserted 5 C ns t 2 sack/ deasserted from sreq/ deasserted 5 C ns t 3 data setup to sack/ asserted 55 C ns t 4 data hold from sreq/ deasserted 20 C ns valid n valid n + 1 n + 1 n + 1 n n t 1 t 2 t 3 t 4 sreq/ sack/ sd[15:0]/, sdp[1:0]/ table 6.40 initiator asynchronous receive symbol parameter min max units t 1 sack/ asserted from sreq/ asserted 5 C ns t 2 sack/ deasserted from sreq/ deasserted 5 C ns t 3 data setup to sreq/ asserted 0 C ns t 4 data hold from sack/ asserted 0 C ns valid n valid n + 1 n + 1 n + 1 n n t 1 t 2 t 3 t 4 sreq/ sack/ sd[15:0]/, sdp[1:0]/
scsi timing diagrams 6-59 figure 6.37 target asynchronous send figure 6.38 target asynchronous receive table 6.41 target asynchronous send symbol parameter min max units t 1 sreq/ deasserted from sack/ asserted 5 C ns t 2 sreq/ asserted from sack/ deasserted 5 C ns t 3 data setup to sreq/ asserted 55 C ns t 4 data hold from sack/ asserted 20 C ns valid n valid n + 1 n + 1 n + 1 n n t 1 t 2 t 3 t 4 sreq/ sack/ sd[15:0]/, sdp[1:0]/ table 6.42 target asynchronous receive symbol parameter min max units t 1 sreq/ deasserted from sack/ asserted 5 C ns t 2 sreq/ asserted from sack/ deasserted 5 C ns t 3 data setup to sack/ asserted 0 C ns t 4 data hold from sreq/ deasserted 0 C ns valid n valid n + 1 n + 1 n + 1 n n t 1 t 2 t 3 t 4 sreq/ sack/ sd[15:0]/, sdp[1:0]/
6-60 speci?cations table 6.43 scsi-1 transfers (se 5.0 mbytes) symbol parameter min max units t 1 send sreq/ or sack/ assertion pulse width 90 C ns t 2 send sreq/ or sack/ deassertion pulse width 90 C ns t 1 receive sreq/ or sack/ assertion pulse width 90 C ns t 2 receive sreq/ or sack/ deassertion pulse width 90 C ns t 3 send data setup to sreq/ or sack/ asserted 55 C ns t 4 send data hold from sreq/ or sack/ asserted 100 C ns t 5 receive data setup to sreq/ or sack/ asserted 0 C ns t 6 receive data hold from sreq/ or sack/ asserted 45 C ns table 6.44 scsi-1 transfers (differential 4.17 mbytes) symbol parameter min max units t 1 send sreq/ or sack/ assertion pulse width 96 C ns t 2 send sreq/ or sack/ deassertion pulse width 96 C ns t 1 receive sreq/ or sack/ assertion pulse width 84 C ns t 2 receive sreq/ or sack/deassertion pulse width 84 C ns t 3 send data setup to sreq/ or sack/ asserted 65 C ns t 4 send data hold from sreq/ or sack/ asserted 110 C ns t 5 receive data setup to sreq/ or sack/ asserted 0 C ns t 6 receive data hold from sreq/ or sack/ asserted 45 C ns
scsi timing diagrams 6-61 table 6.45 scsi-2 fast transfers 10.0 mbytes (8-bit transfers) or 20.0 mbytes (16-bit transfers) 40 mhz clock symbol parameter min max units t 1 send sreq/ or sack/ assertion pulse width 35 C ns t 2 send sreq/ or sack/ deassertion pulse width 35 C ns t 1 receive sreq/ or sack/ assertion pulse width 20 C ns t 2 receive sreq/ or sack/ deassertion pulse width 20 C ns t 3 send data setup to sreq/ or sack/ asserted 33 C ns t 4 send data hold from sreq/ or sack/ asserted 45 C ns t 5 receive data setup to sreq/ or sack/ asserted 0 C ns t 6 receive data hold from sreq/ or sack/ asserted 10 C ns table 6.46 scsi-2 fast transfers 10.0 mbytes (8-bit transfers) or 20.0 mbytes (16-bit transfers) 50 mhz clock 1 symbol parameter 2 min max unit t 1 send sreq/ or sack/ assertion pulse width 35 C ns t 2 send sreq/ or sack/ deassertion pulse width 35 C ns t 1 receive sreq/ or sack/ assertion pulse width 20 C ns t 2 receive sreq/ or sack/ deassertion pulse width 20 C ns t 3 send data setup to sreq/ or sack/ asserted 33 C ns t 4 send data hold from sreq/ or sack/ asserted 40 3 Cns t 5 receive data setup to sreq/ or sack/ asserted 0 C ns t 6 receive data hold from sreq/ or sack/ asserted 10 C ns 1. transfer period bits (bits [6:4] in the scsi transfer (sxfer) register) are set to zero and the extra clock cycle of data setup bit (bit 7 in scsi control one (scntl1) ) is set. 2. note: for fast scsi, set the tolerant enable bit (bit 7 in scsi test three (stest3) ). 3. analysis of system con?guration is recommended due to reduced driver skew margin in differential systems.
6-62 speci?cations table 6.47 ultra scsi se transfers 20.0 mbytes (8-bit transfers) or 40.0 mbytes (16-bit transfers) quadrupled 40 mhz clock 1 1. transfer period bits (bits [6:4] in the scsi transfer (sxfer) register) are set to zero and the extra clock cycle of data setup bit (bit 7 in scsi control one (scntl1) ) is set. symbol parameter 2 2. note: for fast scsi, set the tolerant enable bit (bit 7 in scsi test three (stest3) ). during ultra scsi transfers, the value of the extend req/ack filtering bit ( scsi test two (stest2) , bit 1) has no effect. min max unit t 1 send sreq/ or sack/ assertion pulse width 16 C ns t 2 send sreq/ or sack/ deassertion pulse width 16 C ns t 1 receive sreq/ or sack/ assertion pulse width 10 C ns t 2 receive sreq/ or sack/ deassertion pulse width 10 C ns t 3 send data setup to sreq/ or sack/ asserted 12 C ns t 4 send data hold from sreq/ or sack/ asserted 17 C ns t 5 receive data setup to sreq/ or sack/ asserted 0 C ns t 6 receive data hold from sreq/ or sack/ asserted 6 C ns table 6.48 ultra scsi hvd transfers 20.0 mbytes (8-bit transfers) or 40.0 mbytes (16-bit transfers) 80 mhz clock 1 1. transfer period bits (bits [6:4] in the scsi transfer (sxfer) register) are set to zero and the extra clock cycle of data setup bit (bit 7 in scsi control one (scntl1) ) is set. symbol parameter 2 2. during ultra scsi transfers, the value of the extend req/ack filtering bit ( scsi test two (stest2) , bit 1) has no effect. min max unit t 1 send sreq/ or sack/ assertion pulse width 16 C ns t 2 send sreq/ or sack/ deassertion pulse width 16 C ns t 1 receive sreq/ or sack/ assertion pulse width 10 C ns t 2 receive sreq/ or sack/ deassertion pulse width 10 C ns t 3 send data setup to sreq/ or sack/ asserted 16 C ns t 4 send data hold from sreq/ or sack/ asserted 21 C ns t 5 receive data setup to sreq/ or sack/ asserted 0 C ns t 6 receive data hold from sreq/ or sack/ asserted 6 C ns
scsi timing diagrams 6-63 figure 6.39 initiator and target synchronous transfer table 6.49 ultra2 scsi transfers 40.0 mbyte (8-bit transfers) or 80.0 mbyte (16-bit transfers) quadrupled 40 mhz clock 1 1. transfer period bits (bits [6:4] in the scsi transfer (sxfer) register) are set to zero and the extra clock cycle of data setup bit (bit 7 in scsi control one (scntl1) )isset . symbol parameter 2 2. during ultra2 scsi transfers, the value of the extend req/ack filtering bit ( scsi test two (stest2) , bit 1) has no effect. min max unit t 1 send sreq/ or sack/ assertion pulse width 8 C ns t 2 send sreq/ or sack/ deassertion pulse width 8 C ns t 1 receive sreq/ or sack/ assertion pulse width 6 C ns t 2 receive sreq/ or sack/ deassertion pulse width 6 C ns t 3 send data setup to sreq/ or sack/ asserted 10 C ns t 4 send data hold from sreq/ or sack/ asserted 10 C ns t 5 receive data setup to sreq/ or sack/ asserted 4.5 C ns t 6 receive data hold from sreq/ or sack/ asserted 4.5 C ns valid n valid n + 1 n + 1 n t 1 t 2 t 3 t 4 sreq/ send data receive data sdp[1:0]/ or sack/ sd[15:0]/, sdp[1:0]/ sd[15:0]/, t 5 t 6 valid n + 1 valid n
6-64 speci?cations table 6.50 signal names and bga position a_diffsens a20 a-gpio0_ fetch/ ab16 a_gpio1_ master/y16 a_gpio2 aa16 a_gpio3 ac17 a_gpio4 ab17 a_sack - c13 a_sack+ a14 a_sack2 - b13 a_sack2+ a13 a_satn - b11 a_satn+ b12 a_sbsy - c12 a_sbsy+ a12 a_sc_d - c15 a_sc_d+ a16 a_sd0 - b6 a_sd0+ a6 a_sd1 - c7 a_sd1+ b7 a_sd2 - a7 a_sd2+ c8 a_sd3 - d8 a_sd3+ b8 a_sd4 - a8 a_sd4+ c9 a_sd5 - d9 a_sd5+ b9 a_sd6 - a9 a_sd6+ c10 a_sd7 - d11 a_sd7+ b10 a_sd8 - a18 a_sd8+ b18 a_sd9 - d18 a_sd9+ c18 a_sd10 - a19 a_sd10+ b19 a_sd11 - d19 a_sd11+ c19 a_sd12 - c4 a_sd12+ a3 a_sd13 - b4 a_sd13+ a4 a_sd14 - c5 a_sd14+ d5 a_sd15 - b5 a_sd15+ a5 a_sdp0 - a10 a_sdp0+ c11 a_sdp1 - c6 a_sdp1+ d6 a_si_o - b17 a_si_o+ c17 a_smsg - c14 a_smsg+ a15 a_sreq - c16 a_sreq+ a17 a_sreq2 - b16 a_sreq2+ d16 a_srst - b14 a_srst+ d13 a_ssel - b15 a_ssel+ d15 ack64/ ab1 ad0 y3 ad1 aa1 ad2 y2 ad3 y1 ad4 w3 ad5 w4 ad6 w2 ad7 w1 ad8 v4 ad9 v2 ad10 v1 ad11 u3 ad12 u2 ad13 u1 ad14 t3 ad15 t4 ad16 n3 ad17 n1 ad18 n2 ad19 m2 ad20 m3 ad21 m1 ad22 l2 ad23 l1 ad24 k2 ad25 l4 ad26 k3 ad27 j1 ad28 j2 ad29 j4 ad30 j3 ad31 h1 ad32 ac14 ad33 aa13 ad34 ac13 ad35 ab13 ad36 ab12 ad37 aa12 ad38 ac12 ad39 ab11 ad40 ac11 ad41 aa11 ad42 ac10 ad43 ab10 ad44 y11 ad45 aa10 ad46 ac9 ad47 ab9 ad48 y9 ad49 aa9 ad50 ac8 ad51 ab8 ad52 y8 ad53 aa8 ad54 ac7 ad55 ab7 ad56 aa7 ad57 ac6 ad58 ab6 ad59 y6 ad60 aa6 ad61 ac5 ad62 ab5 ad63 y5 alt_inta/ f1 alt_intb/ g3 b_diffsens y21 b_gpio0_fetch/aa14 b_gpio1_ master/ ac15 b_gpio2 ab15 b_gpio3 aa15 b_gpio4 ac16 b_sack - n20 b_sack+ p21 b_sack2 - p23 b_sack2+ p22 b_satn - m23 b_satn+ n22 b_sbsy - n23 b_sbsy+ n21 b_sc_d - t20 b_sc_d+ t21 b_sd0 - g21 b_sd0+ g22 b_sd1 - g23 b_sd1+ h21 b_sd2 - h20 b_sd2+ h22 b_sd3 - h23 b_sd3+ j21 b_sd4 - j20 b_sd4+ j22 b_sd5 - j23 b_sd5+ k21 b_sd6 - l20 b_sd6+ k22 b_sd7 - k23 b_sd7+ l21 b_sd8 - v21 b_sd8+ w23 b_sd9 - w22 b_sd9+ w20 b_sd10 - w21 b_sd10+ y23 b_sd11 - y22 b_sd11+ aa23 b_sd12 - d22 b_sd12+ d23 b_sd13 - e21 b_sd13+ e20 b_sd14 - e22 b_sd14+ e23 b_sd15 - f21 b_sd15+ f20 b_sdp0 - l23 b_sdp0+ l22 b_sdp1 - f22 b_sdp1+ f23 b_si_o - v22 b_si_o+ v20 b_smsg - r20 b_smsg+ r21 b_sreq - u21 b_sreq+ v23 b_sreq2 - u23 b_sreq2+ u22 b_srst - r23 b_srst+ r22 b_ssel - t23 b_ssel+ t22 c_be0/ v3 c_be1/ t2 c_be2/ p1 c_be3/ k1 c_be4/ ac4 c_be5/ ab4 c_be6/ ac3 c_be7/ aa4 clk h3 devsel/ r1 frame/ p2 gnt/ h4 idsel l3 int_dir g2 inta/ f4 intb/ f2 irdy/ n4 mad0 ac23 mad[1] ab21 mad[2] ac22 mad[3] aa20 mad[4] ab20 mad[5] ac20 mad[6] aa19 mad[7] y19 mas0/ ac18 mas1/ aa17 mce/ aa18 moe/_testout y18 mwe/ ac19 nc a1 nc a2 nc a22 nc a23 nc b1 nc b2 nc b3 nc b21 nc b22 nc b23 nc c2 nc c22 nc d21 nc ac1 nc aa22 nc ac2 nc ab2 nc ab22 nc ab23 nc ab3 pa r t 1 par64 aa5 perr/ r4 rbias m21 req/ h2 req64/ aa2 reserved ab14 rst/ g1 sclk a21 serr/ r3 stop/ r2 tck d1 tdi e2 tdo e1 test_hsc c23 tms e3 trdy/ p3 test_rst/ c1 vdd d10 vdd u20 vdd p20 vdd k20 vdd g20 vdd y17 vdd y14 vdd y10 vdd y7 vdd u4 vdd p4 vdd k4 vdd g4 vdd d17 vdd d7 vdd d14 vdd-a c20 vdd-bias m22 vdd-bias2 a11 vdd-core d3 vdd-core e4 vdd-core y13 vdd-core ab18 vss d20 vss m4 vss y4 vss y12 vss y20 vss m20 vss aa3 vss aa21 vss d12 vss d4 vss k10 vss k11 vss k12 vss k13 vss k14 vss l10 vss l11 vss l12 vss l13 vss l14 vss c21 vss c3 vss m10 vss m11 vss m12 vss m13 vss m14 vss n10 vss n11 vss n12 vss n13 vss n14 vss p10 vss p11 vss p12 vss p13 vss p14 vss-a b20 vss-core d2 vss-core y15 vss-core ab19 vss-core ac21 vss_core f3 signal bga name pos signal bga name pos signal bga name pos signal bga name pos signal bga name pos
scsi timing diagrams 6-65 table 6.51 signal names by bga position nc a1 nc a2 a_sd12+ a3 a_sd13+ a4 a_sd15+ a5 a_sd0+ a6 a_sd2 - a7 a_sd4 - a8 a_sd6 - a9 a_sdp0 - a10 vdd-bias2 a11 a_sbsy+ a12 a_sack2+ a13 a_sack+ a14 a_smsg+ a15 a_sc_d+ a16 a_sreq+ a17 a_sd8 - a18 a_sd10 - a19 a_diffsens a20 sclk a21 nc a22 nc a23 ad1 aa1 req64/ aa2 vss aa3 c_be7/ aa4 par64 aa5 ad60 aa6 ad56 aa7 ad53 aa8 ad49 aa9 ad45 aa10 ad41 aa11 ad37 aa12 ad33 aa13 b_gpio0_ fetch/ aa14 b_gpio3 aa15 a_gpio2 aa16 mas1/ aa17 mce/ aa18 mad[6] aa19 mad[3] aa20 vss aa21 nc aa22 b_sd11+ aa23 ack64/ ab1 nc ab2 nc ab3 c_be5/ ab4 ad62 ab5 ad58 ab6 ad55 ab7 ad51 ab8 ad47 ab9 ad43 ab10 ad39 ab11 ad36 ab12 ad35 ab13 reserved ab14 b_gpio2 ab15 a-gpio0_ fetch/ ab16 a_gpio4 ab17 vdd-core ab18 vss-core ab19 mad[4] ab20 mad[1] ab21 nc ab22 nc ab23 nc ac1 nc ac2 c_be6/ ac3 c_be4/ ac4 ad61 ac5 ad57 ac6 ad54 ac7 ad50 ac8 ad46 ac9 ad42 ac10 ad40 ac11 ad38 ac12 ad34 ac13 ad32 ac14 b_gpio1_ master/ ac15 b_gpio4 ac16 a_gpio3 ac17 mas0/ ac18 mwe/ ac19 mad[5] ac20 vss-core ac21 mad[2] ac22 mad[0] ac23 nc b1 nc b2 nc b3 a_sd13 - b4 a_sd15 - b5 a_sd0 - b6 a_sd1+ b7 a_sd3+ b8 a_sd5+ b9 a_sd7+ b10 a_satn - b11 a_satn+ b12 a_sack2 - b13 a_srst - b14 a_ssel - b15 a_sreq2 - b16 a_si_o - b17 a_sd8+ b18 a_sd10+ b19 vss-a b20 nc b21 nc b22 nc b23 test_rst/ c1 nc c2 vss c3 a_sd12 - c4 a_sd14 - c5 a_sdp1 - c6 a_sd1 - c7 a_sd2+ c8 a_sd4+ c9 a_sd6+ c10 a_sdp0+ c11 a_sbsy - c12 a_sack - c13 a_smsg - c14 a_sc_d - c15 a_sreq - c16 a_si_o+ c17 a_sd9+ c18 a_sd11+ c19 vdd-a c20 vss c21 nc c22 test_hsc c23 tck d1 vss-core d2 vdd-core d3 vss d4 a_sd14+ d5 a_sdp1+ d6 vdd d7 a_sd3 - d8 a_sd5 - d9 vdd d10 a_sd7 - d11 vss d12 a_srst+ d13 vdd d14 a_ssel+ d15 a_sreq2+ d16 vdd d17 a_sd9 - d18 a_sd11 - d19 vss d20 nc d21 b_sd12 - d22 b_sd12+ d23 tdo e1 tdi e2 tms e3 vdd-core e4 b_sd13+ e20 b_sd13 - e21 b_sd14 - e22 b_sd14+ e23 alt_inta/ f1 intb/ f2 vss_core f3 inta/ f4 b_sd15+ f20 b_sd15 - f21 b_sdp1 - f22 b_sdp1+ f23 rst/ g1 int_dir g2 alt_intb/ g3 vdd g4 vdd g20 b_sd0 - g21 b_sd0+ g22 b_sd1 - g23 ad31 h1 req/ h2 clk h3 gnt/ h4 b_sd2 - h20 b_sd1+ h21 b_sd2+ h22 b_sd3- h23 ad27 j1 ad28 j2 ad30 j3 ad29 j4 b_sd4 - j20 b_sd3+ j21 b_sd4+ j22 b_sd5 - j23 c_be3/ k1 ad24 k2 ad26 k3 vdd k4 vss k10 vss k11 vss k12 vss k13 vss k14 vdd k20 b_sd5+ k21 b_sd6+ k22 b_sd7 - k23 ad23 l1 ad22 l2 idsel l3 ad25 l4 vss l10 vss l11 vss l12 vss l13 vss l14 b_sd6 - l20 b_sd7+ l21 b_sdp0+ l22 b_sdp0 - l23 ad21 m1 ad19 m2 ad20 m3 vss m4 vss m10 vss m11 vss m12 vss m13 vss m14 vss m20 rbias m21 vdd-bias m22 b_satn - m23 ad17 n1 ad18 n2 ad16 n3 irdy/ n4 vss n10 vss n11 vss n12 vss n13 vss n14 b_sack - n20 b_sbsy+ n21 b_satn+ n22 b_sbsy - n23 c_be2/ p1 frame/ p2 trdy/ p3 vdd p4 vss p10 vss p11 vss p12 vss p13 vss p14 vdd p20 b_sack+ p21 b_sack2+ p22 b_sack2 - p23 devsel/ r1 stop/ r2 bserr/ r3 perr/ r4 b_smsg - r20 b_smsg+ r21 b_srst+ r22 b_srst - r23 pa r t 1 c_be1/ t2 ad14 t3 ad15 t4 b_sc_d - t20 b_sc_d+ t21 b_ssel+ t22 b_ssel - t23 ad13 u1 ad12 u2 ad11 u3 vdd u4 vdd u20 b_sreq - u21 b_sreq2+ u22 b_sreq2 - u23 ad10 v1 ad9 v2 c_be0/ v3 ad8 v4 b_si_o+ v20 b_sd8 - v21 b_si_o - v22 b_sreq+ v23 ad7 w1 ad6 w2 ad4 w3 ad5 w4 b_sd9+ w20 b_sd10 - w21 b_sd9 - w22 b_sd8+ w23 ad3 y1 ad2 y2 ad0 y3 vss y4 ad63 y5 ad59 y6 vdd y7 ad52 y8 ad48 y9 vdd y10 ad44 y11 vss y12 vdd-core y13 vdd y14 vss-core y15 a_gpio1_ master/ y16 vdd y17 moe/_testout y18 mad[7] y19 vss y20 b_diffsens y21 b_sd11 - y22 b_sd10+ y23 signal bga name pos signal bga name pos signal bga name pos signal bga name pos signal bga name pos
6-66 speci?cations figure 6.40 SYM53C896 329 bga (bottom view)
scsi timing diagrams 6-67 figure 6.41 SYM53C896 329 bga mechanical drawing impor tant: this drawing may not be the latest version. for board layout and manufacturing, obtain the most recent engineering drawings from your lsi logic marketing representative by requesting the outline drawing for package code bl. md98.bl
6-68 speci?cations
symbios SYM53C896 pci to dual channel ultra2 scsi multifunction controller a-1 appendix a register summary table a.1 SYM53C896 register map register name address read/write page pci registers vendor id 0x00C0x01 read only 4-2 device id 0x02C0x03 read only 4-3 command 0x04C0x05 read/write 4-3 status 0x06C0x07 read/write 4-5 revision id (rev id) 0x08 read only 4-6 class code 0x09C0x0b read only 4-7 cache line size 0x0c read/write 4-7 latency timer 0x0d read/write 4-8 header type 0x0e read only 4-8 not supported 0x0f C 4-8 base address register zero (i/o) 0x10C0x13 read/write 4-9 base address register one (memory) 0x14C0x1b read/write 4-9 base address register two (scripts ram) 0x1cC0x23 read/write 4-10 not supported 0x24C0x27 C 4-10 reserved 0x28C0x2b C 4-10 subsystem vendor id 0x2cC0x2d read only 4-11 subsystem id 0x2eC0x2f read only 4-12 expansion rom base address 0x30C0x33 read/write 4-12
a-2 register summary capabilities pointer 0x34 read only 4-13 reserved 0x35C0x3b C 4-13 interrupt line 0x3c read/write 4-14 interrupt pin 0x3d read only 4-14 min_gnt 0x3e read only 4-15 max_lat 0x3f read only 4-15 capability id 0x40 read only 4-16 next item pointer 0x41 read only 4-16 power management capabilities (pmc) 0x42C0x43 read only 4-16 power management control/status (pmcsr) 0x44C0x45 read/write 4-17 bridge support extensions (pmcsr_bse) 0x46 read only 4-18 data 0x47 read only 4-19 scsi registers scsi control zero (scntl0) 0x00 read/write 4-22 scsi control one (scntl1) 0x01 read/write 4-25 scsi control two (scntl2) 0x02 read/write 4-28 scsi control three (scntl3) 0x03 read/write 4-30 scsi chip id (scid) 0x04 read/write 4-32 scsi transfer (sxfer) 0x05 read/write 4-33 scsi destination id (sdid) 0x06 read/write 4-38 general purpose (gpreg) 0x07 read/write 4-38 scsi first byte received (sfbr) 0x08 read/write 4-39 scsi output control latch (socl) 0x09 read/write 4-40 scsi selector id (ssid) 0x0a read only 4-41 scsi bus control lines (sbcl) 0x0b read only 4-42 table a.1 SYM53C896 register map (cont.) register name address read/write page
a-3 dma status (dstat) 0x0c read only 4-42 scsi status zero (sstat0) 0x0d read only 4-45 scsi status one (sstat1) 0x0e read only 4-47 scsi status two (sstat2) 0x0f read only 4-49 data structure address (dsa) 0x10C0x13 read/write 4-51 interrupt status zero (istat0) 0x14 read/write 4-51 interrupt status one (istat1) 0x15 read/write 4-55 mailbox zero (mbox0) 0x16 read/write 4-56 mailbox one (mbox1) 0x17 read/write 4-56 chip test zero (ctest0) 0x18 read/write 4-57 chip test one (ctest1) 0x19 read only 4-57 chip test two (ctest2) 0x1a read only (bit 3 write) 4-58 chip test three (ctest3) 0x1b read/write 4-60 temporary (temp) 0x1cC0x1f read/write 4-61 dma fifo (dfifo) 0x20 read/write 4-61 chip test four (ctest4) 0x21 read/write 4-62 chip test five (ctest5) 0x22 read/write 4-64 chip test six (ctest6) 0x23 read/write 4-66 dma byte counter (dbc) 0x24C0x26 read/write 4-66 dma command (dcmd) 0x27 read/write 4-67 dma next address (dnad) 0x28C0x2b read/write 4-67 dma scripts pointer (dsp) 0x2cC0x2f read/write 4-67 dma scripts pointer save (dsps) 0x30C0x33 read/write 4-68 scratch register a (scratcha) 0x34C0x37 read/write 4-68 dma mode (dmode) 0x38 read only 4-68 table a.1 SYM53C896 register map (cont.) register name address read/write page
a-4 register summary dma interrupt enable (dien) 0x39 read/write 4-71 scratch byte register (sbr) 0x3a read/write 4-72 dma control (dcntl) 0x3b read/write 4-72 adder sum output (adder) 0x3cC0x3f read only 4-75 scsi interrupt enable zero (sien0) 0x40 read/write 4-75 scsi interrupt enable one (sien1) 0x41 read/write 4-77 scsi interrupt status zero (sist0) 0x42 read only 4-79 scsi interrupt status one (sist1) 0x43 read only 4-81 scsi longitudinal parity (slpar) 0x44 read/write 4-82 scsi wide residue (swide) 0x45 read/write 4-84 chip type (ctype) 0x46 read only 4-84 general purpose pin control (gpcntl) 0x47 read/write 4-85 scsi timer zero (stime0) 0x48 read/write 4-86 scsi timer one (stime1) 0x49 read/write 4-88 response id zero (respid0) 0x4a read/write 4-91 response id one (respid1) 0x4b read/write 4-91 scsi test zero (stest0) 0x4c read only 4-92 scsi test one (stest1) 0x4d read/write 4-93 scsi test two (stest2) 0x4e read/write 4-94 scsi test three (stest3) 0x4f read/write 4-96 scsi input data latch (sidl) 0x50C0x51 read only 4-98 scsi test four (stest4) 0x52 read only 4-99 reserved 0x53 C 4-100 scsi output data latch (sodl) 0x54C0x55 read/write 4-100 chip control 0 (ccntl0) 0x56 read/write 4-100 table a.1 SYM53C896 register map (cont.) register name address read/write page
a-5 chip control 1 (ccntl1) 0x57 read/write 4-102 scsi bus data lines (sbdl) 0x58C0x59 read only 4-104 reserved 0x5aC0x5b C 4-104 scratch register b (scratchb) 0x5cC0x5f read/write 4-104 scratch registers cCr (scratchcCscratchr) 0x60C0x9f read/write 4-105 memory move read selector (mmrs) 0xa0C0xa3 read/write 4-106 memory move write selector (mmws) 0xa4C0xa7 read/write 4-107 scripts fetch selector (sfs) 0xa8C0xab read/write 4-107 dsa relative selector (drs) 0xacC0xaf read/write 4-107 static block move selector (sbms) 0xb0C0xb3 read/write 4-108 dynamic block move selector (dbms) 0xb4C0xb7 read/write 4-108 dma next address 64 (dnad64) 0xb8C0xbb read/write 4-108 reserved 0xbcC0xbf C 4-108 phase mismatch jump address 1 (pmjad1) 0xc0C0xc3 read/write 4-109 phase mismatch jump address 2 (pmjad2) 0xc4C0xc7 read/write 4-109 remaining byte count (rbc) 0xc8C0xcb read/write 4-110 updated address (ua) 0xccC0xcf read/write 4-110 entry storage address (esa) 0xd0C0xd3 read/write 4-111 instruction address (ia) 0xd4C0xd7 read/write 4-111 scsi byte count (sbc) 0xd8C0xda read only 4-111 reserved 0xdb C 4-112 cumulative scsi byte count (csbc) 0xdcC0xdf read/write 4-112 reserved 0xe0C0xff C 4-112 table a.1 SYM53C896 register map (cont.) register name address read/write page
a-6 register summary
symbios SYM53C896 pci to dual channel ultra2 scsi multifunction controller b-1 appendix b external memory interface diagram examples figure b.1 16 kbyte interface with 200 ns memory SYM53C896 27c128 moe/ oe mce/ ce d[7:0] 8 mad[7:0] bus ck q[7:0] 8 a[7:0] qe d[5:0] ck q[5:0] qe 6 a[13:8] 6 v dd mas0/ mas1/ 8 note: mad[3:1] pulled low internally. mad bus sense logic enabled for 16 kbyte of slow memory (200 ns devices @ 33 mhz). hct374 hct374 d[7:0] mad0 4.7 k
b-2 external memory interface diagram examples figure b.2 64 kbyte interface with 150 ns memory SYM53C896 27c512-15/ moe/ oe mce/ ce d[7:0] 8 mad[7:0] bus ck q[7:0] 8 a[7:0] qe d[5:0] ck q[5:0] qe 6 a[15:8] 6 v dd mas0/ mas1/ 8 note: mad 3, 1, 0 pulled low internally. mad bus sense logic enabled for 64 kbyte of fast memory (150 ns devices @ 33 mhz). hct374 hct374 gpio4 mwe/ vpp control + 12 v vpp we optional - for flash memory only, not required for eeproms. 28f512-15/ socket d[7:0] mad2 4.7 k
b-3 figure b.3 128, 256, 512 kbyte or 1 mbyte interface with 150 ns memory SYM53C896 27c020-15/ moe/ oe mce/ ce d[7:0] 8 mad[7:0] bus ck q[7:0] 8 a[7:0] qe d[5:0] ck q[5:0] qe 6 a[15:8] 6 v dd mas0/ mas1/ 8 note: mad[2:0] pulled low internally. mad bus sense logic enabled for 128, 256, 512 kbytes, or 1 mbyte of fast memory (150 ns devices @ 33 mhz). the hct374s may be replaced with hct377s. hct374 hct374 gpio4 mwe/ vpp control + 12 v vpp we optional - for flash memory only, not required for eeproms. 28f020-15/ socket d[7:0] mad3 4.7 k d[3:0] ck q[3:0] qe 4 4 hct374 mad[3:0] bus e a[19:16]
b-4 external memory interface diagram examples figure b.4 512 kbyte interface with 150 ns memory SYM53C896 moe/ d[7:0] 8 mad[7:0] bus ck q[7:0] 8 a[7:0] qe d[7:0] ck q[7:0] qe 8 a[15:8] 8 v dd mas0/ mas1/ 8 note: mad[2] pulled low internally. mad bus sense logic enabled for 512 kbytes of slow memory (150 ns devices, additional time required for hct139 @ 33 mhz). the hct374s may be replaced with hct377s. hct374 hct374 gpio4 mwe/ vpp control + 12 v vpp optional - for flash memory only, not required for eeproms. d[7:0] mad3 4.7 k d[2:0] ck q0 q2 3 hct374 mad[2:0] e mad1 4.7 k mad3 4.7 k oe we d[7:0] a0 a16 . . . oe we d[7:0] a0 a16 . . . oe we d[7:0] a0 a16 . . . oe we d[7:0] a0 a16 . . . a b gb y0 y1 y2 y3 mce/ hct139 ce ce ce ce 27c010-15/28f010-15 sockets bus
symbios SYM53C896 pci to dual channel ultra2 scsi multifunction controller ix-1 index symbols (64timod) 4-103 (a7) 5-24 (aap) 4-24 (abrt) 4-43 , 4-51 (ack) 4-40 , 4-42 (adb) 4-25 (adck) 4-64 (adder) 4-75 (aesp) 4-26 (aip) 4-46 (arb[1:0]) 4-22 (art) 4-92 (atn) 4-40 , 4-42 (auxc) 4-17 (aws) 4-95 (baro) 4-9 (bart) 4-10 (barz) 4-9 (bbck) 4-65 (bdis) 4-62 (bf) 4-43 , 4-71 (bl) 4-68 (bl2) 4-65 (bo) 4-61 (bo[9:8]) 4-65 (bof) 4-70 (bse) 4-18 (bsy) 4-40 , 4-42 (c_d) 4-40 , 4-42 , 4-49 (cc) 4-7 (ccf[2:0]) 4-31 (ccntl0) 4-100 (ccntl1) 4-102 (chm) 4-28 (cid) 4-16 (cio) 4-58 (clf) 2-46 , 4-60 (cls) 4-7 (clse) 2-6 , 4-72 (cm) 4-58 (cmp) 2-44 , 4-76 , 4-79 (com) 4-74 (con) 4-26 , 4-53 (cp) 4-13 (csbc) 4-112 (csf) 2-46 , 4-98 (ctest0) 4-57 (ctest1) 4-57 (ctest2) 4-58 (ctest3) 4-60 (ctest4) 4-62 (ctest5) 4-64 (ctest6) 4-66 (ctype) 4-84 (d1s) 4-17 (d2s) 4-17 (dack) 4-59 (data) 4-19 (dbc) 4-66 (dbms) 4-108 (dcmd) 4-67 (dcntl) 4-72 (ddac) 4-102 (ddir) 4-58 , 4-65 (df[7:0]) 4-66 (dfe) 4-43 (dfifo) 4-61 (dfs) 4-65 (dhp) 4-26 (did) 4-3 (dien) 4-71 (dif) 4-95 (diff) 4-50 (dils) 4-101 (diom) 4-70 (dip) 2-43 , 2-46 , 2-48 , 4-54 (dmode) 4-68 (dnad) 4-67 (dnad64) 4-108 (dpe) 4-5 (dpr) 4-6 , 4-102 (dreq) 4-59 (drs) 4-107 (dsa) 4-51 (dscl[1:0]) 4-17 (dsi) 4-17 , 4-97 (dslt[3:0]) 4-18 (dsp) 4-67 (dsps) 4-68 (dstat) 4-42 (dt[1:0]) 4-5 (ebm) 4-4 (eis) 4-4 (ems) 4-4 (en64dbmv) 4-103 (en64tibmv) 4-103 (enc[3:0]) 4-33 , 4-38 (enid) 4-41 (enndj) 4-101 (enpmj) 4-100 (epc) 4-24
ix-2 index (eper) 4-3 (erba) 4-12 (erl) 4-70 (ermp) 4-70 (esa) 4-111 (ews) 4-31 (exc) 4-25 (ext) 4-95 (fbl[2:0]) 4-64 (fbl3) 4-63 (fe) 4-85 (ff[3:0]) 4-47 (ff4) 4-50 (ffl) 4-57 (flf) 4-60 (flsh) 4-55 (fm) 4-60 (fmt) 4-57 (gen) 4-78 , 4-82 (gen[3:0]) 4-89 (gensf) 4-88 (gpcntl) 4-85 (gpio) 4-39 (gpio[1:0]) 4-85 (gpio[4:2]) 4-85 (gpreg) 4-38 (hsc) 4-97 (ht) 4-8 (hth) 4-78 , 4-82 (hth[3:0]) 4-86 (hthba) 4-88 (hthsf) 4-89 (i/o) 4-9 , 4-40 , 4-42 , 4-49 (ia) 4-111 (iarb) 4-27 (iid) 4-44 , 4-71 (il) 4-14 (ilf) 4-45 (ilf1) 4-49 (intf) 4-53 (ip) 4-14 (irm[1:0]) 4-94 (irqd) 4-74 (irqm) 4-74 (iso) 4-93 (istat0) 4-51 (istat1) 4-55 (ldsc) 4-50 (ledc) 4-85 (loa) 4-46 (lock) 4-99 (low) 4-96 (lt) 4-8 (m/a) 4-75 , 4-79 (man) 4-71 (masr) 4-65 (mbox0) 4-56 (mbox1) 4-56 (mdpe) 4-43 , 4-71 (me) 4-85 (memory) 4-9 (mg) 4-15 (ml) 4-15 (mmrs) 4-106 (mmws) 4-107 (mo[4:0]) 4-36 (mpee) 4-63 (msg) 4-40 , 4-42 , 4-49 (nc) 4-6 (nip) 4-16 (olf) 4-45 (olf1) 4-50 (orf) 4-45 (orf1) 4-49 (par) 4-77 , 4-81 (pcicie) 4-58 (pen) 4-18 (pfen) 4-73 (pff) 4-73 (pmc) 4-16 (pmcsr) 4-17 (pmcsr_bse) 4-18 (pmec) 4-17 (pmes) 4-16 (pmjad1) 4-109 (pmjad2) 4-109 (pmjctl) 4-101 (pst) 4-17 (pws[1:0]) 4-18 (qen) 4-93 (qsel) 4-94 (rbc) 4-110 (req) 4-40 , 4-42 (respid0) 4-91 (respid1) 4-91 (rid) 4-6 (rma) 4-5 (rof) 4-95 (rre) 4-32 (rsl) 4-76 , 4-80 (rst) 4-26 , 4-46 , 4-77 , 4-81 (rta) 4-5 (s16) 4-97 (sbc) 4-111 (sbcl) 4-42 (sbdl) 4-104 (sbmc) 4-77 , 4-82 (sbms) 4-108 (sbr) 4-72 (sce) 4-94 (scf[2:0]) 4-31 (scid) 4-32 (sclk) 4-93 (scntl0) 4-22 (scntl1) 4-25 (scntl2) 4-28 (scntl3) 4-30 (scratcha) 4-68 (scratchb) 4-104 (scratchcCscratchr) 4-105 (scripts ram) 4-10 (sdid) 4-38 (sdp0) 4-46 (sdp0l) 4-49 (sdp1) 4-51 (sdu) 4-28 (se) 4-3 (sel) 4-40 , 4-42 , 4-76 , 4-79 (sem) 4-52 (sfbr) 4-39 (sfs) 4-107 (sge) 4-76 , 4-80
index ix-3 (si) 4-55 (sid) 4-12 (sien0) 4-75 (sien1) 4-77 (sigp) 4-52 , 4-58 (sip) 4-54 (sir) 4-43 , 4-71 (sist0) 4-79 (sist1) 4-81 (slb) 4-95 (slpar) 4-82 (slphben) 4-29 (slpmd) 4-29 (slt) 4-92 (smode[1:0]) 4-99 (socl) 4-40 (sodl) 4-100 (som) 4-93 (soz) 4-92 (spl1) 4-50 (sre) 4-32 (srst) 4-52 (srtm) 4-63 (srun) 4-55 (ssaid) 4-92 (sse) 4-5 (ssi) 4-43 , 4-71 (ssid) 4-41 (ssm) 4-73 (sst) 4-27 (sstat0) 4-45 (sstat1) 4-47 (sstat2) 4-49 (start) 4-23 (std) 4-74 (stest0) 4-92 (stest1) 4-93 (stest2) 4-94 (stest3) 4-96 (stest4) 4-99 (stime0) 4-86 (stime1) 4-88 (sto) 4-78 , 4-82 (str) 4-97 (stw) 4-98 (swide) 4-84 (sxfer) 4-33 (szm) 4-95 (te) 4-96 (temp) 4-61 (teop) 4-59 (tp[2:0]) 4-33 (trg) 4-24 (ttm) 4-98 (typ) 4-84 (ua) 4-110 (udc) 4-77 , 4-80 (use) 4-30 (v) 4-60 (val) 4-41 (ver[2:0]) 4-17 (vue0) 4-29 (vue1) 4-30 (watn) 4-24 (wie) 4-4 (woa) 4-46 (wrie) 4-61 (wsr) 4-30 (wss) 4-29 (zmod) 4-102 (zsd) 4-63 numerics 16-bit system (s16) 4-97 32/64-bit jump 5-31 32-bit addressing 5-6 3-state 3-3 64 kbytes rom read cycle 6-56 , 6-57 64-bit addressing 5-7 addressing in scripts 2-20 script selectors 4-106 table indirect indexing mode (64timod) 4-103 8-bit/16-bit scsi 2-35 a a and b diffsens scsi signals 6-3 a[6:0] 5-23 a_diffsens 3-14 a_gpio0_ fetch/ 3-11 a_gpio1_ master/ 3-11 a_gpio2 3-11 a_gpio3 3-11 a_gpio4 3-11 a_sack+- 3-15 a_sack2+- 3-15 a_satn+- 3-15 a_sbsy+- 3-15 a_sc_d+- 3-15 a_sctrl signals 3-15 a_sd[15:0]+- 3-14 a_sdp[1:0]+- 3-14 a_si_o+- 3-15 a_smsg+- 3-15 a_sreq+- 3-15 a_sreq2+- 3-15 a_srst+- 3-15 a_ssel+- 3-15 aborted (abrt) 4-43 , 4-51 , 4-71 absolute maximum stress ratings 6-1 ac characteristics 6-11 ack64/ 3-7 acknowledge 64 3-7 active negation see tolerant technology active termination 2-37 ad[63:0] 3-6 adder sum output (adder) 4-75 address and data signals 3-6 address/data bus 2-3 alt interrupt a 3-10 b 3-10 alt_inta/ 3-10 alt_intb/ 3-10 always wide scsi (aws) 4-95 arbitration in progress (aip) 4-46 mode bits 1 and 0 (arb[1:0]) 4-22 priority encoder test (art) 4-92
ix-4 index signals 3-8 assert even scsi parity (force bad parity) (aesp) 4-26 satn/ on parity error (aap) 4-24 scsi ack/ signal (ack) 4-40 , 4-42 atn/ signal (atn) 4-40 , 4-42 bsy/ signal (bsy) 4-40 , 4-42 c_d/ signal (c_d) 4-40 , 4-42 data bus (adb) 4-25 i_o/ signal (i/o) 4-40 , 4-42 msg/ signal (msg) 4-40 , 4-42 req/ signal (req) 4-40 , 4-42 rst/ signal (rst) 4-26 sel/ signal (sel) 4-40 , 4-42 asynchronous scsi receive 2-31 send 2-29 aux_current 4-17 b b_diffsens 3-17 b_gpio0_fetch/ 3-12 b_gpio1_master/ 3-12 b_gpio2 3-12 b_gpio3 3-12 b_gpio4 3-12 b_sack+- 3-18 b_sack2+- 3-18 b_satn+- 3-18 b_sbsy+- 3-18 b_sc_d+- 3-18 b_sd[15:0]+- 3-16 b_sdp[1:0]+- 3-16 b_si_o+- 3-18 b_smsg+- 3-18 b_sreq+- 3-18 b_sreq2+- 3-18 b_srst+- 3-18 b_ssel+- 3-18 back-to-back read 32-bits address and data 6-26 back-to-back write 32-bits address and data 6-28 base address register one (baro) 2-3 , 4-9 two (bart) 4-10 zero (barz) 2-3 , 4-9 bidirectional 3-3 signals 6-4 , 6-5 bios 2-3 bits used for parity control and generation 2-26 block move 2-9 instructions 5-4 bridge support extensions (bse) 4-18 burst disable (bdis) 4-62 length (bl) 4-68 length bit 2 (bl2) 4-65 opcode fetch 32-bits address and data 6-24 opcode fetch enable (bof) 4-70 size selection 2-7 burst read 32-bits address and data 6-30 64-bits address and data 6-32 burst write 32-bits address and data 6-34 64-bits address and data 6-36 bus command and byte enables 3-6 fault (bf) 4-43 , 4-71 byte count 5-39 empty in dma fifo (fmt) 4-57 full in dma fifo (ffl) 4-57 offset counter (bo) 4-61 c c_be[3:0]/ 2-3 c_be[7:0]/ 3-6 cache line size (cls) 2-7 , 4-7 enable (clse) 2-7 , 4-72 register 2-6 , 2-10 cache mode, see pci cache mode 2-10 call instruction 5-28 cap_id (cid) 4-16 capabilities pointer (cp) 4-13 capability id register 4-16 carry test 5-31 chained block moves 2-51 scripts instruction 2-52 sodl register 2-52 swide register 2-52 wide scsi receive bit 2-51 wide scsi send bit 2-51 chained mode (chm) 4-28 change bus phases 2-18 chip control 0 (ccntl0) 4-100 control 1 (ccntl1) 4-102 revision level (v) 4-60 test five (ctest5) 2-7 , 4-64 test four (ctest4) 2-26 , 4-62 test one (ctest1) 4-57 test six (ctest6) 4-66 test three (ctest3) 2-8 , 2-11 , 4-60 test two (ctest2) 4-58 test zero (ctest0) 4-57 type (ctype) 4-84 type (typ) 4-84 chmov 2-51 class code register 4-7 clear dma fifo (clf) 2-46 , 4-60 clear instruction 5-17 , 5-18 clear scsi fifo (csf) 2-46 , 4-98 clk 3-5 clock 3-5 address incrementor (adck) 4-64 byte counter (bbck) 4-65 conversion factor (ccf[2:0]) 4-31 quadrupler 2-22 command register 4-3 compare data 5-32 phase 5-32 configuration read command 2-5 space 2-3
index ix-5 write command 2-6 configured as i/o (cio) 4-58 as memory (cm) 4-58 connected (con) 4-26 , 4-53 cumulative scsi byte count (csbc) 4-112 current function of input voltage 6-9 function of output voltage 6-10 cycle frame 3-7 d d1_support (d1s) 4-17 d2_support (d2s) 4-17 data (data) 4-19 acknowledge status (dack) 4-59 compare mask 5-32 compare value 5-33 parity error reported (dpr) 4-6 paths 2-29 request status (dreq) 4-59 structure address (dsa) 4-51 transfer direction (ddir) 4-58 data_scale (dscl[1:0]) 4-17 data_select (dslt[3:0]) 4-18 data-in 2-52 , 2-53 data-out 2-52 , 2-53 dc characteristics 6-1 decode of mad pins 3-24 default download mode 2-57 destination address 5-24 i/o-memory enable (diom) 4-70 detected parity error (from slave) (dpe) 4-5 determining data transfer rate 2-39 device id (did) 4-3 select 3-8 specific initialization (dsi) 4-17 devsel/ 3-8 timing (dt[1:0]) 4-5 diffsens mismatch (diff) 4-50 dip 2-46 direct 5-20 disable auto fifo clear (disfc) 4-101 dual address cycle (ddac) 4-102 halt on parity error or atn (target only) (dhp) 4-26 internal load/store (dils) 4-101 pipe req (dpr) 4-102 single initiator response (dsi) 4-97 disconnect 2-18 disconnect instruction 5-16 dma byte counter (dbc) 4-66 command (dcmd) 4-67 control (dcntl) 2-6 , 2-7 , 2-8 , 2-44 , 4-72 direction (ddir) 4-65 fifo 2-8 , 2-28 , 2-43 (df[7:0]) 4-66 (dfifo) 4-61 byte offset counter, bits [9:8] (bo[9:8]) 4-65 empty (dfe) 4-43 sections 2-29 size (dfs) 4-65 interrupt 2-44 , 2-45 , 2-46 enable (dien) 2-26 , 2-43 , 2-45 , 4-71 interrupt pending (dip) 4-54 interrupts 2-46 mode (dmode) 2-6 , 2-7 , 2-8 , 2-11 , 2-23 , 4-68 next address (dnad) 4-67 next address 64 (dnad64) 4-108 scripts pointer (dsp) 4-67 pointer save (dsps) 4-68 status (dstat) 2-26 , 2-42 , 2-43 , 2-46 , 2-47 , 2-48 , 4-42 dsa relative 5-38 relative selector (drs) 4-107 dsps register 5-36 dual address cycles 2-20 dynamic block move selector (dbms) 4-108 e enable 64-bit direct bmov (en64dbmv) 4-103 table indirect bmov (en64tibmv) 4-103 bus mastering (ebm) 4-4 i/o space (eis) 4-4 jump on nondata phase mismatches (enndj) 4-101 memory space (ems) 4-4 parity checking 2-25 checking (epc) 4-24 error response (eper) 4-3 phase mismatch jump (enpmj) 4-100 read line (erl) 4-70 multiple (ermp) 4-70 response to reselection (rre) 4-32 selection (sre) 4-32 wide scsi (ews) 4-31 enabling cache mode 2-10 encoded chip scsi id (enc[3:0]) 4-33 destination scsi id (enc[3:0]) 4-38 (enid) 4-41 scsi destination id 5-21 entry storage address (esa) 4-111 error reporting signals 3-9 even parity 2-25 expansion rom base address 2-55 , 2-56 , 4-12 extend sreq/sack filtering (ext) 4-95 external clock 6-11 memory interface 2-55 configuration 2-56 diagram examples b-1 multiple byte accesses 6-13 slow memory 2-56 memory read 6-38 memory timing 6-38 memory write 6-41 extra clock cycle of data setup (exc) 4-25
ix-6 index f fetch enable (fe) 4-85 pin mode (fm) 4-60 fifo byte control (fbl[2:0]) 4-64 byte control (fbl3) 4-63 flags (ff[3:0]) 4-47 flags, bit 4 (ff4) 4-50 first dword 5-5 , 5-15 , 5-23 , 5-27 , 5-38 flush dma fifo (flf) 4-60 flushing (flsh) 4-55 frame/ 3-7 frequency lock (lock) 4-99 full arbitration, selection/reselection 4-23 function complete 2-44 (cmp) 4-76 , 4-79 g general description 1-1 general purpose (gpreg) 4-38 i/o (gpio) 4-39 i/o pin 0 3-11 , 3-12 i/o pin 1 3-11 , 3-12 i/o pin 2 3-11 , 3-12 i/o pin 3 3-11 , 3-12 i/o pin 4 3-11 , 3-12 pin control (gpcntl) 4-85 timer expired (gen) 2-44 , 4-78 , 4-82 timer period (gen[3:0]) 4-89 timer scale factor (gensf) 4-88 gnt/ 2-10 , 3-8 gpio enable (gpio[1:0]) 4-85 gpio enable (gpio[4:2]) 4-85 grant 3-8 h halt scsi clock (hsc) 4-97 halting 2-47 handshake-to-handshake timer bus activity enable (hthba) 4-88 timer expired (hth) 2-44 , 4-78 , 4-82 timer period (hth[3:0]) 4-86 timer scale factor (hthsf) 4-89 hardware control of scsi activity led 2-20 hardware interrupts 2-41 header type (ht) 4-8 high impedance mode (zmod) 4-102 high voltage differential interface 2-35 high voltage differential mode autoswitching with lvd and single-ended mode 2-33 description 2-33 hvd or se/lvd (dif) 4-95 hvd signals 2-34 i i/o 3-3 instructions 5-15 read command 2-5 space 2-3 write command 2-5 idsel 2-3 , 3-8 signal 2-6 illegal instruction detected (iid) 4-44 , 4-71 immediate arbitration (iarb) 4-27 data 5-24 indirect addressing 5-5 initialization device select 3-8 initiator asynchronous receive 6-58 asynchronous send 6-58 mode 5-11 , 5-17 phase mismatch 4-79 ready 3-7 synchronous transfer 6-63 timing 6-22 input 3-3 capacitance 6-3 current as a function of input voltage 6-9 signals 6-5 instruction address (ia) 4-111 prefetch unit flushing 2-22 type 5-38 block move 5-5 i/o instruction 5-15 memory move 5-35 read/write instruction 5-23 transfer control instruction 5-27 int_dir 3-10 inta routing enable 3-23 inta, intb disable (irqd) 4-74 inta/ 2-42 , 2-45 , 2-48 , 3-10 , 3-23 intb/ 2-42 , 2-45 , 2-48 , 3-10 , 3-23 interface 128, 256, 512 kbyte or 1 mbyte 150 ns memory b-3 16 kbyte 200 ns memory b-1 512 kbyte 150 ns memory b-4 64 kbyte 150 ns memory b-2 control signals 3-7 internal arbiter 2-10 scripts ram 2-19 internal ram see also scripts ram 2-19 interrupt a 3-10 acknowledge command 2-5 b 3-10 direction 3-10 handling 2-41 instruction 5-29 line 4-14 on-the-fly (in) 5-31 on-the-fly (intf) 4-53 output 6-12 pin (ip) 4-14 request 2-42 routing mode (irm[1:0]) 4-94 signals 3-10 status one (istat1) 2-42 , 4-55
index ix-7 status zero (istat0) 2-42 , 4-51 interrupt-on-the-fly instruction 5-29 interrupts 2-44 fatal vs. nonfatal interrupts 2-44 halting 2-47 masking 2-45 sample interrupt service routine 2-47 stacked interrupts 2-46 irdy/ 3-7 irq mode (irqm) 4-74 issuing cache commands 2-11 j jtag boundary scan testing 2-24 jump address 5-33 call a relative address 5-30 call an absolute address 5-30 control (pmjctl) 4-101 if true/false 5-31 instruction 5-27 jump64 address 5-33 l last disconnect (ldsc) 4-50 latched scsi parity (sdp0l) 4-49 for sd[15:8] (spl1) 4-50 latency 2-9 timer (lt) 4-8 led_cntl (ledc) 4-85 load and store instructions prefetch unit and store instructions 2-23 load/store 5-39 load/store instructions 2-24 , 5-37 loopback enable 2-25 lost arbitration (loa) 4-46 low voltage differential see lvd link 2-33 lvd driver scsi signals 6-2 receiver scsi signals 6-3 scsi 1-4 lvd link 1-1 , 1-4 benefits 1-4 operation 2-33 m mad bus 2-56 bus programming 3-23 pins 2-56 mad[0] 3-24 mad[3:1] 3-23 mad[4] 3-23 mad[5] 3-23 mad[6] 3-23 mad[7:0] 3-19 , 3-23 mad[7] 3-23 mailbox one (mbox1) 2-42 , 4-56 mailbox zero (mbox0) 2-42 , 4-56 manual start mode (man) 4-71 mas0/ 3-19 mas1/ 3-19 masking 2-45 master control for set or reset pulses (masr) 4-65 data parity error (mdpe) 4-43 , 4-71 enable (me) 4-85 parity error enable (mpee) 4-63 max scsi synchronous offset (mo[4:0]) 4-36 max_lat (ml) 4-15 maximum stress ratings 6-1 mce/ 3-19 memory address strobe 0 3-19 address strobe 1 3-19 address/data bus 3-19 chip enable 3-19 i/o address/dsa offset 5-39 move 2-9 move instructions 2-23 , 5-34 no flush option 2-23 move read selector (mmrs) 4-106 move write selector (mmws) 4-107 output enable 3-19 , 3-20 read 2-11 read caching 2-11 read command 2-5 read line 2-10 , 2-12 read line command 2-7 read multiple 2-10 , 2-12 read multiple command 2-6 space 2-3 to memory 2-17 to memory moves 2-17 write 2-11 , 2-12 write and invalidate 2-10 write and invalidate command 2-8 write caching 2-12 write command 2-5 write enable 3-19 min_gnt (mg) 4-15 moe/_testout 3-19 , 3-20 move to/from sfbr cycles 5-24 multiple cache line transfers 2-9 mwe/ 3-19 n new capabilities (nc) 4-6 new features in the SYM53C896 1-3 next item pointer register 4-16 next_item_ptr (nip) 4-16 no download mode 2-58 no flush 5-35 store instruction only 5-39 nonburst opcode fetch 32-bits address and data 6-22 normal/fast memory ( 128 kbytes) multiple byte access read cycle 6-48 multiple byte access write cycle 6-50 single byte access read cycle 6-44 single byte access write cycle 6-46 o opcode 5-10 , 5-15 , 5-23 , 5-27 fetch burst capability 2-23
ix-8 index operating conditions 6-2 operating register/scripts ram read 32-bits 6-17 64-bits 6-18 operating register/scripts ram write 32-bits 6-19 64-bits 6-20 operator 5-23 output current as a function of output voltage 6-10 output signals 6-4 , 6-6 p par 3-6 par64 3-7 parallel rom interface 2-55 parallel rom support 2-56 parity 2-27 , 3-6 error 3-9 (par) 4-81 options 2-25 parity64 3-7 pci addressing 2-3 bus commands and encoding types 2-4 bus commands and functions supported 2-4 cache line size register 2-8 cache mode 2-10 command register 2-8 commands 2-4 configuration info enable (pcicie) 4-58 configuration register read 6-15 configuration register write 6-16 configuration registers 4-1 configuration space 2-3 external memory interface timing diagrams 6-13 functional description 2-2 i/o space 2-3 interface signals 3-5 master transaction 2-11 master transfer 2-11 memory space 2-3 performance 1-7 target disconnect 2-9 target retry 2-9 perr/ 3-9 phase mismatch handling in scripts 2-19 jump address 1 (pmjad1) 4-109 jump address 2 (pmjad2) 4-109 jump registers 4-109 physical dword address and data 3-6 pme clock (pmec) 4-17 enable (pen) 4-18 status (pst) 4-17 support (pmes) 4-16 polling 2-41 power and ground signals 3-21 management 2-58 capabilities 4-16 control/status 4-17 state (pws[1:0]) 4-18 state d0 2-59 state d1 2-59 state d2 2-60 state d3 2-60 prefetch enable (pfen) 4-73 flush 2-23 flush (pff) 4-73 scripts instructions 2-22 pull-ups, internal, conditions 3-4 r ram, see also scripts ram 2-19 rbias 3-22 read line 2-10 , 2-11 line function 2-7 modify-write cycles 5-24 multiple 2-8 , 2-10 , 2-11 multiple with read line enabled 2-8 write instructions 5-23 write system memory from scripts 5-35 read/write instructions 5-23 , 5-25 system memory from scripts 5-35 received master abort (from master) (rma) 4-5 target abort (from master) (rta) 4-5 register address 5-39 address - a[6:0] 5-23 register map a-1 registers 2-42 relative 5-20 relative addressing mode 5-19 , 5-30 remaining byte count (rbc) 4-110 req/ 2-10 , 3-8 req/ - gnt/ 2-2 req64/ 3-7 request 3-8 request 64 3-7 reselect 2-18 during reselection 2-38 instruction 5-15 reselected (rsl) 2-44 , 4-76 , 4-80 reserved command 2-5 reset 3-5 input 6-12 scsi offset (rof) 4-95 response id one (respid1) 4-91 response id zero (respid0) 4-91 return instruction 5-28 revision id register 4-6 (rid) 4-6 rise and fall time test condition 6-8 rom flash and memory interface signals 3-19 interface 2-55 pin 2-56 rst/ 3-5 s sack 2-47 sacs 2-20 sclk 3-13
index ix-9 quadrupler enable (qen) 4-93 quadrupler select (qsel) 4-94 scratch byte register (sbr) 4-72 register a (scratcha) 4-68 register b (scratchb) 4-104 registers cCr (scratchcCscratchr) 4-105 script fetch selector (sfs) 4-107 scripts instruction 2-51 interrupt instruction received (sir) 4-43 , 4-71 processor 2-18 internal ram for instruction storage 2-19 performance 2-18 ram 2-4 , 2-19 running (srun) 4-55 scsi atn condition - target mode (m/a) 4-75 bit mode change (sbmc) 4-82 bus control lines (sbcl) 4-42 bus data lines (sbdl) 4-104 bus interface 2-32 , 2-39 bus mode change (sbmc) 4-77 byte count (sbc) 4-111 c_d/ signal (c_d) 4-49 chip id (scid) 4-32 clock (sclk) 3-13 , 4-93 control enable (sce) 4-94 control one (scntl1) 2-26 , 4-25 control three (scntl3) 2-39 , 2-40 , 4-30 control two (scntl2) 2-51 , 4-28 control zero (scntl0) 2-26 , 4-22 cumulative byte count 4-112 data high impedance (zsd) 4-63 destination id (sdid) 4-38 disconnect unexpected (sdu) 4-28 encoded destination id 5-21 fifo test read (str) 4-97 fifo test write (stw) 4-98 first byte received (sfbr) 4-39 function a control 3-15 function a gpio signals 3-11 function a signals 3-13 function b control 3-18 function b gpio signals 3-12 function b signals 3-16 functional description 2-18 gross error (sge) 4-76 , 4-80 hysteresis of receivers 6-9 i_o/ signal (i/o) 4-49 input data latch (sidl) 4-98 input filtering 6-8 instructions block move 5-4 i/o 5-15 read/write 5-23 interface signals 3-13 interrupt enable one (sien1) 2-43 , 4-77 interrupt enable zero (sien0) 2-26 , 2-43 , 4-75 interrupt pending (sip) 4-54 interrupt status one (sist1) 2-42 , 2-43 , 2-46 , 2-47 , 4-81 interrupt status zero (sist0) 2-26 , 2-42 , 2-43 , 2-46 , 2-47 , 4- 79 interrupts 2-46 isolation mode (iso) 4-93 longitudinal parity (slpar) 4-82 loopback mode (slb) 2-25 , 4-95 low level mode (low) 4-96 lvd link 2-33 mode (smode[1:0]) 4-99 msg/ signal (msg) 4-49 output control latch (socl) 4-40 output data latch (sodl) 2-51 , 2-52 , 2-53 , 4-100 parity control 2-27 parity error (par) 4-77 parity errors and interrupts 2-27 performance 1-6 phase 5-12 , 5-29 phase mismatch - initiator mode 4-75 registers 4-20 reset condition (rst) 4-77 rst/ received (rst) 4-81 rst/ signal (rst) 4-46 scripts operation 5-1 sample instruction 5-3 sdp0/ parity signal (sdp0) 4-46 sdp1/ parity signal (sdp1) 4-51 selected as id (ssaid) 4-92 selector id (ssid) 4-41 serial eeprom access 2-57 status one (sstat1) 2-26 , 4-47 status two (sstat2) 2-26 , 4-49 status zero (sstat0) 2-26 , 4-45 synchronous offset maximum (som) 4-93 synchronous offset zero (soz) 4-92 synchronous transfer period (tp[2:0]) 4-33 termination 2-37 test four (stest4) 4-99 test one (stest1) 4-93 test three (stest3) 4-96 test two (stest2) 2-25 , 4-94 test zero (stest0) 4-92 timer one (stime1) 4-88 timer zero (stime0) 4-86 timing diagrams 6-58 tolerant technology 1-5 transfer (sxfer) 2-40 , 4-33 true end of process 4-59 ultra2 scsi 2-21 valid (val) 4-41 wide residue (swide) 2-52 , 4-84 scsi high impedance mode (szm) 4-95 scsi-1 transfers (differential 4.17 mbytes) 6-60 (single-ended 5.0 mbytes) 6-60 scsi-2 fast transfers 10.0 mbytes (8-bit transfers) 40 mhz clock 6-61 50 mhz clock 6-61 20.0 mbytes (16-bit transfers) 40 mhz clock 6-61 50 mhz clock 6-61 second dword 5-14 , 5-22 , 5-24 , 5-33 , 5-36 , 5-39 select 2-18 during selection 2-38 instruction 5-17 with atn/ 5-21 with satn/ on a start sequence (watn) 4-24 selected (sel) 2-44 , 4-76 , 4-79 selection or reselection time-out (sto) 4-78 , 4-82
ix-10 index selection response logic test (slt) 4-92 semaphore (sem) 4-52 serial eeprom data format 2-58 interface 2-57 serr/ 3-9 serr/ enable (se) 4-3 set instruction 5-16 , 5-18 set/clear carry 5-21 sack/ 5-21 satn/ 5-22 target mode 5-21 shadow register test mode (srtm) 4-63 sidl least significant byte full (ilf) 4-45 most significant byte full (ilf1) 4-49 signal names and bga position 6-64 by bga position 6-64 signal process (sigp) 4-52 , 4-58 signaled system error (sse) 4-5 simple arbitration 4-22 single address cycles 2-20 ended scsi signals 6-7 step interrupt (ssi) 4-43 , 4-71 step mode (ssm) 4-73 sip 2-43 , 2-46 slow memory ( 128 kbytes) read cycle 6-52 write cycle 6-54 slow rom pin 3-24 slpar high byte enable (slphben) 4-29 slpar mode (slpmd) 4-29 sodl least significant byte full (olf) 4-45 most significant byte full (olf1) 4-50 register 2-52 sodr least significant byte full (orf) 4-45 most significant byte full (orf1) 4-49 software reset (srst) 4-52 source i/o-memory enable (siom) 4-69 special cycle command 2-5 sreq 2-47 stacked interrupts 2-46 start address 5-14 , 5-22 dma operation (std) 4-74 scsi transfer (sst) 4-27 sequence (start) 4-23 static block move selector (sbms) 4-108 status register 4-5 stop command 2-9 stop signal 3-8 stop/ 3-8 store instruction 2-23 stress ratings 6-1 subsystem id 2-58 (sid) 4-12 subsystem vendor id 2-58 (svid) 4-11 swide register 2-52 sym53c700 compatibility (com) 4-74 SYM53C896 329 ball grid array 6-66 329 bga mechanical drawing 6-67 new features 1-3 register map a-1 sync_irqd (si) 4-55 synchronous clock conversion factor (scf[2:0]) 4-31 data transfer rates 2-39 operation 2-39 scsi receive 2-31 scsi send 2-30 system error 3-9 system signals 3-5 t table indirect 5-6 , 5-20 mode 5-19 table relative 5-20 target asynchronous receive 6-59 asynchronous send 6-59 mode 5-10 , 5-15 satn/ active (m/a) 4-79 mode (trg) 4-24 ready 3-7 synchronous transfer 6-63 timing 6-15 tck 3-20 tdi 3-20 tdo 3-20 temp register 5-37 temporary (temp) 4-61 termination 2-37 test clock 3-20 test data in 3-20 test data out 3-20 test halt scsi clock 3-20 test interface signals 3-20 test mode select 3-20 test reset 3-20 test_hsc 3-20 test_rstn 3-20 third dword 5-14 , 5-33 , 5-36 timer test mode (ttm) 4-98 tms 3-20 tolerant 1-5 enable (te) 4-96 technology 1-5 benefits 1-5 electrical characteristics 6-7 totem pole output 3-3 transfer control 2-23 control instructions 5-27 and scripts instruction prefetching 2-23 count 5-35 counter 5-13 information 2-18 rate synchronous 2-39 trdy/ 2-9 , 3-7 u ultra scsi
index ix-11 clock conversion factor bits 4-32 enable (use) 4-30 high voltage differential transfers 20.0 mbytes (8-bit transfers) 80 mhz clock 6-62 40.0 mbytes (16-bit transfers) 80 mhz clock 6-62 single-ended transfers 20.0 mbytes (8-bit transfers) quadrupled 40 mhz clock 6-62 40.0 mbytes (16-bit transfers) quadrupled 40 mhz clock 6-62 ultra2 scsi 1-4 benefits 1-4 designing an ultra2 scsi system 2-21 lvd link 2-33 synchronous data transfers 2-40 transfers 40.0 mbytes (8-bit transfers) quadrupled 40 mhz clock 6-63 80.0 mbytes (16-bit transfers) quadrupled 40 mhz clock 6-63 unexpected disconnect (udc) 4-77 , 4-80 updated address (ua) 4-110 upper register address line (a7) 5-24 use data8/sfbr 5-23 v vdd 3-21 -a 3-21 -bias 3-21 -bias2 3-21 -core 3-21 vendor id (vid) 4-2 unique enhancement, bit 1 (vue1) 4-30 unique enhancements, bit 0 (vue0) 4-29 version (ver[2:0]) 4-17 vss 3-21 -a 3-21 -core 3-21 w wait disconnect instruction 5-18 for disconnect 2-18 for valid phase 5-32 reselect instruction 5-18 select instruction 5-16 wide scsi chained block moves 2-51 receive (wsr) 4-30 receive bit 2-51 send (wss) 4-29 send bit 2-51 won arbitration (woa) 4-46 write read instructions 5-23 read system memory from scripts 5-35 write and invalidate 2-9 , 2-10 , 2-11 enable (wie) 4-4 enable (wrie) 4-61 wsr bit 2-52 wss flag 2-51
ix-12 index
symbios SYM53C896 pci to dual channel ultra2 scsi multifunction controller customer feedback we would appreciate your feedback on this document. please copy the following page, add your comments, and fax it to us at the number shown. if appropriate, please also fax copies of any marked-up pages from this document. impor tant: please include your name, phone number, fax number, and company address so that we may contact you directly for clari?cation or additional information. thank you for your help in improving the quality of our documents.
customer feedback readers comments fax your comments to: lsi logic corporation technical publications m/s e-198 fax: 408.433.4333 please tell us how you rate this document: symbios? SYM53C896 pci to dual channel ultra2 scsi multifunction controller technical manual. place a check mark in the appropriate blank for each category. what could we do to improve this document? if you found errors in this document, please specify the error and page number. if appropriate, please fax a marked-up copy of the page(s). please complete the information below so that we may contact you directly for clari?cation or additional information. excellent good average fair poor completeness of information ____ ____ ____ ____ ____ clarity of information ____ ____ ____ ____ ____ ease of ?nding information ____ ____ ____ ____ ____ technical content ____ ____ ____ ____ ____ usefulness of examples and illustrations ____ ____ ____ ____ ____ overall manual ____ ____ ____ ____ ____ name date telephone title company name street city, state, zip department mail stop fax
u.s. distributors by state a. e. avnet electronics http://www.hh.avnet.com b. m. bell microproducts, inc. (for habs) http://www.bellmicro.com i. e. insight electronics http://www.insight-electronics.com w. e. wyle electronics http://www.wyle.com alabama daphne i. e. tel: 334.626.6190 huntsville a. e. tel: 256.837.8700 i. e. tel: 256.830.1222 w. e. tel: 800.964.9953 alaska a. e. tel: 800.332.8638 arkansas w. e. tel: 972.235.9953 arizona phoenix a. e. tel: 480.736.7000 b. m. tel: 602.267.9551 w. e. tel: 800.528.4040 tempe i. e. tel: 480.829.1800 tucson a. e. tel: 520.742.0515 california agoura hills b. m. tel: 818.865.0266 irvine a. e. tel: 949.789.4100 b. m. tel: 949.470.2900 i. e. tel: 949.727.3291 w. e. tel: 800.626.9953 los angeles a. e. tel: 818.594.0404 w. e. tel: 800.288.9953 sacramento a. e. tel: 916.632.4500 w. e. tel: 800.627.9953 san diego a. e. tel: 858.385.7500 b. m. tel: 858.597.3010 i. e. tel: 800.677.6011 w. e. tel: 800.829.9953 san jose a. e. tel: 408.435.3500 b. m. tel: 408.436.0881 i. e. tel: 408.952.7000 santa clara w. e. tel: 800.866.9953 woodland hills a. e. tel: 818.594.0404 westlake village i. e. tel: 818.707.2101 colorado denver a. e. tel: 303.790.1662 b. m. tel: 303.846.3065 w. e. tel: 800.933.9953 englewood i. e. tel: 303.649.1800 connecticut cheshire a. e. tel: 203.271.5700 i. e. tel: 203.272.5843 wallingford w. e. tel: 800.605.9953 delaware north/south a. e. tel: 800.526.4812 tel: 800.638.5988 b. m. tel: 302.328.8968 w. e. tel: 856.439.9110 florida altamonte springs b. m. tel: 407.682.1199 i. e. tel: 407.834.6310 boca raton i. e. tel: 561.997.2540 clearwater i. e. tel: 727.524.8850 fort lauderdale a. e. tel: 954.484.5482 w. e. tel: 800.568.9953 miami b. m. tel: 305.477.6406 orlando a. e. tel: 407.657.3300 w. e. tel: 407.740.7450 tampa w. e. tel: 800.395.9953 st. petersburg a. e. tel: 727.507.5000 georgia atlanta a. e. tel: 770.623.4400 b. m. tel: 770.980.4922 w. e. tel: 800.876.9953 duluth i. e. tel: 678.584.0812 hawaii a. e. tel: 800.851.2282 idaho a. e. tel: 801.365.3800 w. e. tel: 801.974.9953 illinois north/south a. e. tel: 847.797.7300 tel: 314.291.5350 chicago b. m. tel: 847.413.8530 w. e. tel: 800.853.9953 schaumburg i. e. tel: 847.885.9700 indiana fort wayne i. e. tel: 219.436.4250 w. e. tel: 888.358.9953 indianapolis a. e. tel: 317.575.3500 iowa w. e. tel: 612.853.2280 cedar rapids a. e. tel: 319.393.0033 kansas w. e. tel: 303.457.9953 kansas city a. e. tel: 913.663.7900 lenexa i. e. tel: 913.492.0408 kentucky w. e. tel: 937.436.9953 central/northern/ western a. e. tel: 800.984.9503 tel: 800.767.0329 tel: 800.829.0146 louisiana w. e. tel: 713.854.9953 north/south a. e. tel: 800.231.0253 tel: 800.231.5575 maine a. e. tel: 800.272.9255 w. e. tel: 781.271.9953 maryland baltimore a. e. tel: 410.720.3400 w. e. tel: 800.863.9953 columbia b. m. tel: 800.673.7461 i. e. tel: 410.381.3131 massachusetts boston a. e. tel: 978.532.9808 w. e. tel: 800.444.9953 burlingtonr i. e. tel: 781.270.9400 marlborough b. m. tel: 508.480.9099 woburn b. m. tel: 781.933.9010 michigan brighton i. e. tel: 810.229.7710 detroit a. e. tel: 734.416.5800 w. e. tel: 888.318.9953 minnesota champlin b. m. tel: 800.557.2566 eden prairie b. m. tel: 800.255.1469 minneapolis a. e. tel: 612.346.3000 w. e. tel: 800.860.9953 st. louis park i. e. tel: 612.525.9999 mississippi a. e. tel: 800.633.2918 w. e. tel: 256.830.1119 missouri w. e. tel: 630.620.0969 st. louis a. e. tel: 314.291.5350 i. e. tel: 314.872.2182 montana a. e. tel: 800.526.1741 w. e. tel: 801.974.9953 nebraska a. e. tel: 800.332.4375 w. e. tel: 303.457.9953 nevada las vegas a. e. tel: 800.528.8471 w. e. tel: 702.765.7117 new hampshire a. e. tel: 800.272.9255 w. e. tel: 781.271.9953 new jersey north/south a. e. tel: 201.515.1641 tel: 609.222.6400 mt. laurel i. e. tel: 609.222.9566 pine brook w. e. tel: 800.862.9953 parsippany i. e. tel: 973.299.4425 wayne w. e. tel: 973.237.9010 new mexico w. e. tel: 480.804.7000 albuquerque a. e. tel: 505.293.5119
u.s. distributors by state (continued) new york hauppauge i. e. tel: 516.761.0960 long island a. e. tel: 516.434.7400 w. e. tel: 800.861.9953 rochester a. e. tel: 716.475.9130 i. e. tel: 716.242.7790 w. e. tel: 800.319.9953 smithtown b. m. tel: 800.543.2008 syracuse a. e. tel: 315.449.4927 north carolina raleigh a. e. tel: 919.859.9159 i. e. tel: 919.873.9922 w. e. tel: 800.560.9953 north dakota a. e. tel: 800.829.0116 w. e. tel: 612.853.2280 ohio cleveland a. e. tel: 216.498.1100 w. e. tel: 800.763.9953 dayton a. e. tel: 614.888.3313 i. e. tel: 937.253.7501 w. e. tel: 800.575.9953 strongsville b. m. tel: 440.238.0404 valley view i. e. tel: 216.520.4333 oklahoma w. e. tel: 972.235.9953 tulsa a. e. tel: 918.459.6000 i. e. tel: 918.665.4664 oregon beavertonr b. m. tel: 503.524.0787 i. e. tel: 503.644.3300 portland a. e. tel: 503.526.6200 w. e. tel: 800.879.9953 pennsylvania mercer i. e. tel: 412.662.2707 pittsburgh a. e. tel: 412.281.4150 w. e. tel: 440.248.9996 philadelphia a. e. tel: 800.526.4812 b. m. tel: 215.741.4080 w. e. tel: 800.871.9953 rhode island a. e. 800.272.9255 w. e. tel: 781.271.9953 south carolina a. e. tel: 919.872.0712 w. e. tel: 919.469.1502 south dakota a. e. tel: 800.829.0116 w. e. tel: 612.853.2280 tennessee w. e. tel: 256.830.1119 east/west a. e. tel: 800.241.8182 tel: 800.633.2918 texas austin a. e. tel: 512.219.3700 b. m. tel: 512.258.0725 i. e. tel: 512.719.3090 w. e. tel: 800.365.9953 dallas a. e. tel: 214.553.4300 b. m. tel: 972.783.4191 w. e. tel: 800.955.9953 el paso a. e. tel: 800.526.9238 houston a. e. tel: 713.781.6100 b. m. tel: 713.917.0663 w. e. tel: 800.888.9953 richardson i. e. tel: 972.783.0800 rio grande valley a. e. tel: 210.412.2047 stafford i. e. tel: 281.277.8200 utah centerville b. m. tel: 801.295.3900 murray i. e. tel: 801.288.9001 salt lake city a. e. tel: 801.365.3800 w. e. tel: 800.477.9953 vermont a. e. tel: 800.272.9255 w. e. tel: 716.334.5970 virginia a. e. tel: 800.638.5988 w. e. tel: 301.604.8488 washington kirkland i. e. tel: 425.820.8100 seattle a. e. tel: 425.882.7000 w. e. tel: 800.248.9953 west virginia a. e. tel: 800.638.5988 wisconsin milwaukee a. e. tel: 414.513.1500 w. e. tel: 800.867.9953 wauwatosa i. e. tel: 414.258.5338 wyoming a. e. tel: 800.332.9326 w. e. tel: 801.974.9953
direct sales representatives by state (component and hab) e. a. earle associates e. l. electrodyne - ut grp group 2000 i. s. in?nity sales, inc. ion ion associates, inc. r. a. rathsburg associ- ates, inc. sgy synergy associates, inc. arizona tempe e. a. tel: 480.921.3305 california calabasas i. s. tel: 818.880.6480 irvine i. s. tel: 714.833.0300 san diego e. a. tel: 619.278.5441 illinois elmhurst r. a. tel: 630.516.8400 indiana cicero r. a. tel: 317.984.8608 ligonier r. a. tel: 219.894.3184 plain?eld r. a. tel: 317.838.0360 massachusetts burlington sgy tel: 781.238.0870 michigan byron center r. a. tel: 616.554.1460 good rich r. a. tel: 810.636.6060 novi r. a. tel: 810.615.4000 north carolina cary grp tel: 919.481.1530 ohio columbus r. a. tel: 614.457.2242 dayton r. a. tel: 513.291.4001 independence r. a. tel: 216.447.8825 pennsylvania somerset r. a. tel: 814.445.6976 texas austin ion tel: 512.794.9006 arlington ion tel: 817.695.8000 houston ion tel: 281.376.2000 utah salt lake city e. l. tel: 801.264.8050 wisconsin muskego r. a. tel: 414.679.8250 saukville r. a. tel: 414.268.1152
sales of?ces and design resource centers lsi logic corporation corporate headquarters tel: 408.433.8000 fax: 408.433.8989 north america california costa mesa - mint technology tel: 949.752.6468 fax: 949.752.6868 irvine tel: 949.809.4600 fax: 949.809.4444 pleasanton design center tel: 925.730.8800 fax: 925.730.8700 san diego tel: 858.467.6981 fax: 858.496.0548 silicon valley tel: 408.433.8000 fax: 408.954.3353 wireless design center tel: 858.350.5560 fax: 858.350.0171 colorado boulder tel: 303.447.3800 fax: 303.541.0641 colorado springs tel: 719.533.7000 fax: 719.533.7020 fort collins tel: 970.223.5100 fax: 970.206.5549 florida boca raton tel: 561.989.3236 fax: 561.989.3237 georgia alpharetta tel: 770.753.6146 fax: 770.753.6147 illinois oakbrook terrace tel: 630.954.2234 fax: 630.954.2235 kentucky bowling green tel: 270.793.0010 fax: 270.793.0040 maryland bethesda tel: 301.897.5800 fax: 301.897.8389 massachusetts waltham tel: 781.890.0180 fax: 781.890.6158 burlington - mint technology tel: 781.685.3800 fax: 781.685.3801 minnesota minneapolis tel: 612.921.8300 fax: 612.921.8399 new jersey red bank tel: 732.933.2656 fax: 732.933.2643 cherry hill - mint technology tel: 609.489.5530 fax: 609.489.5531 new york fairport tel: 716.218.0020 fax: 716.218.9010 north carolina raleigh tel: 919.785.4520 fax: 919.783.8909 oregon beaverton tel: 503.645.0589 fax: 503.645.6612 texas austin tel: 512.388.7294 fax: 512.388.4171 plano tel: 972.244.5000 fax: 972.244.5001 houston tel: 281.379.7800 fax: 281.379.7818 canada ontario ottawa tel: 613.592.1263 fax: 613.592.3253 international france paris lsi logic s.a. immeuble europa tel: 33.1.34.63.13.13 fax: 33.1.34.63.13.19 germany munich lsi logic gmbh tel: 49.89.4.58.33.0 fax: 49.89.4.58.33.108 stuttgart tel: 49.711.13.96.90 fax: 49.711.86.61.428 italy milano lsi logic s.p.a. tel: 39.039.687371 fax: 39.039.6057867 japan tokyo lsi logic k.k. tel: 81.3.5463.7821 fax: 81.3.5463.7820 osaka tel: 81.6.947.5281 fax: 81.6.947.5287 korea seoul lsi logic corporation of korea ltd tel: 82.2.528.3400 fax: 82.2.528.2250 the netherlands eindhoven lsi logic europe ltd tel: 31.40.265.3580 fax: 31.40.296.2109 singapore singapore lsi logic pte ltd tel: 65.334.9061 fax: 65.334.4749 tel: 65.835.5040 fax: 65.732.5047 sweden stockholm lsi logic ab tel: 46.8.444.15.00 fax: 46.8.750.66.47 taiwan taipei lsi logic asia, inc. taiwan branch tel: 886.2.2718.7828 fax: 886.2.2718.8869 united kingdom bracknell lsi logic europe ltd tel: 44.1344.426544 fax: 44.1344.481039 sales of?ces with design resource centers
international distributors australia new south wales reptechnic pty ltd tel: 612.9953.9844 fax: 612.9953.9683 belgium acal nv/sa tel: 32.2.7205983 fax: 32.2.7251014 china beijing lsi logic international services inc. tel: 86.10.6804.2534 fax: 86.10.6804.2521 france rungis cedex azzurri technology france tel: 33.1.41806310 fax: 33.1.41730340 germany haar ebv elektronik tel: 49.89.4600980 fax: 49.89.46009840 munich avnet emg gmbh tel: 49.89.45110102 fax: 49.89.42.27.75 wuennenberg-haaren peacock ag tel: 49.2957.79.1692 fax: 49.2957.79.9341 hong kong hong kong avt industrial ltd tel: 852.2428.0008 fax: 852.2401.2105 eastele tel: 852.2798.8860 fax: 852.2305.0640 india bangalore spike technologies india private ltd tel: 91.80.664.5530 fax: 91.80.664.9748 israel tel aviv eastronics ltd tel: 972.3.6458777 fax: 972.3.6458666 japan tokyo global electronics corporation tel: 81.3.3260.1411 fax: 81.3.3260.7100 technical center tel: 81.471.43.8200 yokohama-city macnica corporation tel: 81.45.939.6140 fax: 81.45.939.6141 the netherlands eindhoven acal nederland b.v. tel: 31.40.2.502602 fax: 31.40.2.510255 switzerland brugg lsi logic sulzer ag tel: 41.32.3743232 fax: 41.32.3743233 taiwan taipei avnet-mercuries corporation, ltd tel: 886.2.2516.7303 fax: 886.2.2505.7391 lumax international corporation, ltd tel: 886.2.2788.3656 fax: 886.2.2788.3568 prospect technology corporation, ltd tel: 886.2.2721.9533 fax: 886.2.2773.3756 serial semiconductor corporation, ltd tel: 886.2.2579.5858 fax: 886.2.2570.3123 united kingdom maidenhead azzurri technology ltd tel: 44.1628.826826 fax: 44.1628.829730 swindon ebv elektronik tel: 44.1793.849933 fax: 44.1793.859555 sales of?ces with design resource centers

▲Up To Search▲

Price & Availability of SYM53C896

	To Download SYM53C896 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .